Likelihood to Recommend Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a
Kubernetes based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.
Read full review Red Hat OpenShift overall is a pretty fantastic product. However, I think there is a steep learning curve for administrators of the clusters, and a complicated configuration depending on the amount of integrations. Also, the cost of standing up clusters has perpetually increased, which has become a rather expensive endeavor especially when talking about machine learning,
Read full review Pros One of the biggest advantages is the flexibility to change underlying EC2 instances. As the traffic or demand increases, we can easily change EC2 instances without any issues. Amazon ECS APIs are extremely robust and one can start and stop containers by firing one post request only. So, it is not mandatory to keep the demo solutions up for every time. Just at the time of demo fire the command - make the container up and running - do the demo - down the container with API. A simple portal can control every container which helps non-technical (sales, marketing) to do the demo without keeping the solutions up for the entire time frame. Read full review Obviously, it does container orchestration very well because it's the main purpose of the product. Creating routes has been very easy with the product, creating accessible routes, managing quotas, managing our workspace and our workload has been very efficient with this as well as managing our horizontal scalability. Read full review Cons A cleaner container service road map It would be. nice to have more AI recommended cluster reductions The UX could use some simplification Read full review Upgrades can be stressful to watch - often cluster operators report that they are failing even though the upgrade is proceeding without issue. Native observability is lacking. The canned dashboards are great, but to really dive into an issue, you need to be proficient in PromQL or have a third-party product installed for correlation. It would be nice to be able to review logs for containers that have been removed, at least for a few hours after they're gone. Instead we have to rely on log aggregators to view historic details. Read full review Likelihood to Renew Leverage OpenShift Online constantly at both the free and paid tiers. While AWS is convenient, it often brings more administration than I want to deal with for a quick application (i.e. Drupal or Wordpress blog). OpenShift also simplifies the DNS registration and ability to share application environments with team members
Read full review Usability As I said before, the obserability is one of the weakest point of OpenShift and that has a lot to do with usability. The Kibana console is not fully integrated with OpenShift console and you have to switch from tab to tab to use it. Same with Prometheus, Jaeger and Grafan, it's a "simple" integration but if you want to do complex queries or dashboards you have to go to the specific console
Read full review Performance Applications deployed to OpenShift clusters stay responsive when peak load hits or when the traffic dies down - since the platform reacts by scaling out or scaling in the deployed applications elastically - achieved through' policy sense and response automation - leveraging monitoring, measuring (metrics), auto-scaling to meet SLAs, SLOs, and SLIs. This approach works for stateless or stateful business logic hosting applications. The deployed applications perform consistently, stably, and securely across many deployment platforms - public clouds, private data centers, at the edge, or on factory floors - hosted by bare metal or virtual environments.
Read full review Support Rating Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.
Read full review Their customer support team is good and quick to respond. On a couple of occassions, they have helped us in solving some issues which we were finding a tad difficult to comprehend. On a rare occasion, the response was a bit slow but maybe it was because of the festival season. Overall a good experience on this front.
Read full review Alternatives Considered EKS is a
Kubernetes technology and you need to learn
Kubernetes and build a cluster before using it. So there's a learning curve here. ECS was easier to implement and simpler to have in our use case. It takes less time to run a workload and make it available.
Read full review We've done work on Docker and we've done work in
Podman , which aren't really apples to apples as far as OpenShift because they're just purely containerization tools. They're not necessarily platforms. We did an evaluation on a tool, another Kubernetes-based tool, and I don't even remember the name of it. I cannot think of the name of this tool. It's a VMware tool. I don't remember. They have a Kubernetes solution that they offer. But as far as the features, functionality, and cost of ownership, OpenShift outshines those others that we've looked at. So it seems to be the market leader.
Read full review Contract Terms and Pricing Model It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
Read full review Return on Investment We achieved minimum downtime. The autoscaling kept the performance of the services great. We saved money by running the workloads on AWS ECS in Fargate mode by having different settings for different services to save on the hardware configuration side as well as having scheduled tasks. Read full review We never faced any major outage with the OpenShift platform. It's been running fine except for our network timeouts. That's it for this. It's not about, the pods themselves are running fine, but identifying this kind of issue hasn't been easy, but it didn't have any real business impact. It is just about other sre just to better serve our client and improve the platform's reliability. Read full review ScreenShots