What do you like best?
It just works. Nice UI to setup components and environments which eliminates the complexity of setting up and managing AWS directly. Allows me to worry about the code instead of the underlying deployment infrastructure. The support staff has been great at responding to incidents and proactively taking measures to ensure our application remains available. The CLi tools are well documented when these operations are required (setting configuration, database tunneling, manual deployments). Having it based on git deployments helps with our existing workflow and inherently provides another remote backup location in case of disaster recovery.
Docker has been equally nice to have in that each application components only needs what it needs to operate leaving much less on the server to worry about in terms of vulnerabilities (that we had with our dedicated server). These containers have proven to be very fast and their zero-downtime deployments are critical to our continuous integration process.
What do you dislike?
Getting started with Docker was a little tough, they do not provide much support on setting up the actual Docker & Proc files based on your requirements, but as time has gone on, its become easier and I've gotten good support on setting up additional modules.
Recommendations to others considering the product:
Great for smaller startups who need HIPAA-compliancy and a scalable cloud-based infrastructure but do not have the resources internally to maintain people on staff. If you are looking at running containers but don't know exactly how the orchestration works, this is a better, easier alternative than Heroku
What problems are you solving with the product? What benefits have you realized?
Scalability. We went from a dedicated server to a multi-component HIPAA-compliant infrastructure. This has helped streamline our devops and helps with the sales and marketing aspects of selling a health sensitive related application.