Overview
Search…
⌃K
Links

Container orchestrators

Multiple container orchestration technologies for ease of consumption
DuploCloud abstracts the complexity of container orchestration technologies, allowing you to focus on the deployment, updating, and debugging of your containerized application.
Among the technologies supported are:
  • Kubernetes (AWS Elastic Kubernetes Service [EKS]): DuploCloud platform uses AWS EKS, providing you with a user-friendly interface that conceals the complexities of Kubernetes. Using the UI you can add K8S configurations around POD, Container, Secrets, and so on.
  • Built-in (DuploCloud): DuploCloud platform's built-in container management has the same interface as the docker run command, except that it can be scaled to hundreds of containers across many hosts, providing capabilities such as associated load balancers, DNS, and more.
  • AWS ECS Fargate: Fargate is a technology that you can use with Elastic Container Service (ECS) to run containers without having to manage servers or clusters of EC2 instances.

Container orchestration feature matrix

Use the feature matrix below to compare the features of the orchestration technologies that DuploCloud supports. Whatever option you choose, DuploCloud helps you implement it through the Portal or the Terraform API.
One dot indicates a low rating, two dots indicate a medium rating, and three dots indicate a high rating. For example, Kubernetes has a low ease-of-use rating, but a high rating for stateful applications.
Feature
Kubernetes
Built-In
ECS Fargate
Ease of use
Features and ecosystem Tools
Suitability for stateful apps
Stability and maintenance
AWS cost
Multi-cloud (w/o DuploCloud)

Feature definitions

Use the definitions below to understand how each feature in the matrix above is rated in relation to each of the three listed technologies (Kubernetes, Built-In, ECS Fargate).
  • Ease of Use:
    • Kubernetes is extensible and customizable, but not without a cost in ease of use. The DuploCloud platform reduces the complexities of Kubernetes, making it comparable with other container orchestration technologies in ease of adoption.
    • DuploCloud's Built-in orchestration mirrors docker run. You can SSH into a virtual machine (VM) and run docker commands to debug and diagnose. If you have an application with a few stateless microservices; or configurations that use environment variables or AWS services such as SSM, S3, or Secret store, consider using DuploCloud's Built-in container orchestration.
    • ECS Fargate contains proprietary constructs (such as task definitions, tasks, or services) that can be hard to learn. As Fargate is serverless, you have no control over the Host Docker, so commands such asdocker ps and docker restart are unavailable, making debugging a container crash very difficult and time-consuming. DuploCloud makes using Fargate much simpler with an out-of-the-box setup for logging, shell access, and abstraction of proprietary constructs and behavior.
  • Features and Ecosystem Tools: Kubernetes is rich in many additional built-in features and ecosystem tools, most notably Secrets Management and ConfigMaps. Built-In and ECS rely on native AWS services such as AWS Secrets Manager, SSM, S3, and so on. While Kubernetes features have an equivalent in AWS, third parties tend to publish their software as Kubernetes packages (Helm Charts). Some examples are Influx DB, Time Series DB, Prefect, etc.
  • Suitability for Stateful apps: Stateful applications should be avoided in AWS. Instead, Cloud-managed storage solutions should be leveraged for the best availability and SLA compliance. In scenarios where this is undesirable due to cost, then Kubernetes offers the best solution. Kubernetes uses StatefulSets and Volumes to implicitly manage EBS volumes. With Built-in and ECS, you must use a shared EFS drive, which may not have feature parity with Kubernetes volume management.
  • Stability and Maintenance: Even though Kubernetes is highly stable, it is an open-source product. The native customizability and extensibility of Kubernetes can lead to points of failure when a mandatory cluster upgrade is needed, for example. This complexity often leads to support costs from third-party vendors. Maintenance can be especially costly with EKS, as versions are deprecated frequently and you are required to upgrade the control plane and data nodes. While DuploCloud automates this upgrade process, it still requires careful planning and execution.
  • AWS Cost: While the EKS control plane cost is relatively low, it is not recommended to operate an EKS environment without business support at an additional premium. If you are a small business, you may be able to add the support tier when you need it and then turn it off to reduce costs.
  • Multi-Cloud: For many enterprises and independent software vendors this is a requirement, either immediately or in the future. While Kubernetes provides this benefit, DuploCloud's implementation is much easier to maintain and easier to implement.