Overall, I would rate the solution a six out of ten. From a management perspective, it's not better than NetApp StorageGRID. The price is not better. Also, the initial configuration isn't as straightforward. The system requires improvement there.
My advice to those considering this product is that it's very important to know what platforms you will be integrating with the solution. The integrations are a principal part of the use case. Some people think that HCP can be used like a traditional storage solution, but it doesn't work like that. You have to interrupt the offerability matrix to make sure that you can do the integration. I think that is the most important part. I think this is a comfortable and secure product. I would rate it as a nine out of ten.
This is a great solution, it's reliable, but you must be aware that if the application is critical for the customer, you will need to have deep in-house knowledge, or hire a special team to do the design. I rate Hitachi Content Platform an eight out of ten.
Owning Principal Consultant at a tech services company with 10,001+ employees
Real User
2021-12-23T21:07:00Z
Dec 23, 2021
I used to work at Hitachi, so I'm deeply familiar with what their offering looks like, and from a competitive standpoint, historically, it's where Dell, EMC's, etc., come from. I have more experience with the Hitachi content platform. I helped in the acquisition of the company that Hitachi had or Hitachi pursued to actually make the product. My experience is with version nine of this solution. They have a new product called HCP for Cloud Scale: It's their whole new architecture which I'm not as familiar with. That's how all these companies tend to go to market. There may be some things around IoT, but at the end of the day, the overriding concern is the cost to store. The least costly per terabyte the better. All of these companies, when you amortize it between three to five years, the pricing looks very similar, or they have to look very similar to AWS S3. My advice to others looking into implementing this solution is to not assume it's only hardware. People will make an assumption that it's only hardware-based and it's not. You can buy a software edition of it, and I think their newer product is even more flexible from a software perspective. They may view Hitachi as just a hardware supplier, but they're not only hardware. Hitachi has done a lot of work in rolling upgrades, expansions recovery from failures, etc., which are fundamental to the product. On a scale of one to ten, I'd put it at a seven, but I don't think there's any product in the category that would be beyond a seven.
Senior Consulting Engineer at a tech services company with 501-1,000 employees
Real User
2020-03-30T07:58:00Z
Mar 30, 2020
The best way to integrate that liaison is to use the REST API. That is the best way. Hitachi provides some connectors if other users can use the REST API and integrate that application, that will be a huge advantage for them. Also, you should have programming knowledge to help the application teams integrate the applications with the solution, it will be much easier for the implementation. I would rate it a nine out of ten. The only issue is that the user interface is not so good. Other than that, everything is perfect.
Head of Systems at a tech services company with 501-1,000 employees
Real User
2020-03-16T06:56:19Z
Mar 16, 2020
I have seen that some of our customers position this solution as a file server but this is not something that I recommend. It is not intended as a file server. My advice to anybody who is considering this product is to properly consider the integration between components, or the "glue". This is a good solution but it works as a part of a larger system. If it isn't planned properly then it can be a bit painful. I would rate this solution a nine out of ten.
Head of Systems at a tech services company with 501-1,000 employees
Real User
2020-03-16T06:56:00Z
Mar 16, 2020
I would advise anyone using this solution to get proper glue. You have one product and you will be using it for some purpose, but you need the glue to stitch them together. You need to find the right glue. For that process, when you have to have the right glue and you come up with a complete solution - Hitachi can be a bit painful. Additionally, they need to come up with a simple migration. Writing a proper data migration from an existing system to migrate, that is something that they lack. On a scale of one to ten, I would rate Hitachi Content Platform about a nine.
What is the difference between objects and files? Objects are large collections of data collecting or storing items. Files are a single potential piece within an object.
Overall, I would rate the solution a six out of ten. From a management perspective, it's not better than NetApp StorageGRID. The price is not better. Also, the initial configuration isn't as straightforward. The system requires improvement there.
It is a good product. It is less expensive compared to other technologies like EMC. I rate it a ten out of ten.
My advice to those considering this product is that it's very important to know what platforms you will be integrating with the solution. The integrations are a principal part of the use case. Some people think that HCP can be used like a traditional storage solution, but it doesn't work like that. You have to interrupt the offerability matrix to make sure that you can do the integration. I think that is the most important part. I think this is a comfortable and secure product. I would rate it as a nine out of ten.
This is a great solution, it's reliable, but you must be aware that if the application is critical for the customer, you will need to have deep in-house knowledge, or hire a special team to do the design. I rate Hitachi Content Platform an eight out of ten.
I rate Hitachi Content Platform eight out of 10. I would recommend it.
I used to work at Hitachi, so I'm deeply familiar with what their offering looks like, and from a competitive standpoint, historically, it's where Dell, EMC's, etc., come from. I have more experience with the Hitachi content platform. I helped in the acquisition of the company that Hitachi had or Hitachi pursued to actually make the product. My experience is with version nine of this solution. They have a new product called HCP for Cloud Scale: It's their whole new architecture which I'm not as familiar with. That's how all these companies tend to go to market. There may be some things around IoT, but at the end of the day, the overriding concern is the cost to store. The least costly per terabyte the better. All of these companies, when you amortize it between three to five years, the pricing looks very similar, or they have to look very similar to AWS S3. My advice to others looking into implementing this solution is to not assume it's only hardware. People will make an assumption that it's only hardware-based and it's not. You can buy a software edition of it, and I think their newer product is even more flexible from a software perspective. They may view Hitachi as just a hardware supplier, but they're not only hardware. Hitachi has done a lot of work in rolling upgrades, expansions recovery from failures, etc., which are fundamental to the product. On a scale of one to ten, I'd put it at a seven, but I don't think there's any product in the category that would be beyond a seven.
The best way to integrate that liaison is to use the REST API. That is the best way. Hitachi provides some connectors if other users can use the REST API and integrate that application, that will be a huge advantage for them. Also, you should have programming knowledge to help the application teams integrate the applications with the solution, it will be much easier for the implementation. I would rate it a nine out of ten. The only issue is that the user interface is not so good. Other than that, everything is perfect.
I have seen that some of our customers position this solution as a file server but this is not something that I recommend. It is not intended as a file server. My advice to anybody who is considering this product is to properly consider the integration between components, or the "glue". This is a good solution but it works as a part of a larger system. If it isn't planned properly then it can be a bit painful. I would rate this solution a nine out of ten.
I would advise anyone using this solution to get proper glue. You have one product and you will be using it for some purpose, but you need the glue to stitch them together. You need to find the right glue. For that process, when you have to have the right glue and you come up with a complete solution - Hitachi can be a bit painful. Additionally, they need to come up with a simple migration. Writing a proper data migration from an existing system to migrate, that is something that they lack. On a scale of one to ten, I would rate Hitachi Content Platform about a nine.