To Compose or Not Compose
February 21, 2018
To Compose or Not Compose
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with IBM Compose
We use the redis and elasticsearch services. We utilize these by our application services platform. We do not have IT personnel (and don't plan to) thus we prefer hosted/"as a service" platforms/products. We may focus our energies and spend on our product development not IT operations.
- Excellent Dashboard - easy to use and manage our services
- Excellent Diagnostics - providing up to the second visibility into the status services
- High Availability and redundancy is excellent.
- Honestly - the only con could be cost vs. some other hosted solutions. But comparing apples to apples it's typically just a little higher premium above others.
- The ROI has been good. Again, as a hosted service we are not in the biz of maintaining IT operations - rather we're spending $$ on product development. So if you compare a Dev-Ops engineer to cost of a hosted solution, the ROI is significant for smaller business.
We currently use both Heroku and Compose. Heroku is our PAAS choice for our application servers. As mentioned, previously, the cost of some compose services for development / staging / testing servers was getting costly. For these type of servers we don't need the high availability / redudancy / scalability. As such we chose components through Heroku Add-ons.