DevOps Tooling
Elastic Path Self-Managed Commerce is most often run as Docker-style containers. Elastic Path provides tools to help Self-Managed Commerce customers accomplish DevOps tasks, including:
- Configure Self-Managed Commerce build hosts.
- Build Self-Managed Commerce code.
- Run Self-Managed Commerce tests.
- Build Self-Managed Commerce container images.
- Run Self-Managed Commerce test environments using docker-compose.
- Provision Amazon Elastic Kubernetes Service (EKS) clusters for deploying production-like Self-Managed Commerce environments.
Self-Managed Commerce Build Tools
The Self-Managed Commerce build tooling is a set of components that you can use to perform common Self-Managed Commerce Maven build tasks, invoke Maven tests, and build container images. These tools are designed so you can use them on your local linux environment or integrate them in your continuous integration (CI) system of choice.
| DevOps Feature | Is it provided by this tool? |
|---|---|
| Build host configuration tooling | Yes |
| Maven build tooling | Yes |
| Container image build tooling | Yes |
| Docker-Compose deployment examples | Yes |
| Provision CI infrastructure | No |
| Provision deployment infrastructure | No |
| Container orchestrator | No |
| Application deployment automation | No |
The Self-Managed Commerce build tools supersede the Elastic Path Docker Project. For more information about the Self-Managed Commerce build tools, see Build Tooling Overview.
Infrastructure suitable for running containerized enterprise applications can be used to run Self-Managed Commerce containers built by these tools. For more information about configuring and running Self-Managed Commerce containers, see Containerization.
Elastic Path Docker
The Elastic Path Docker project contains tool that you can use to build container images. These tools are designed so you can use them on your local linux environment or integrate them in your continuous integration (CI) system of choice.
| DevOps Feature | Is it provided by this tool? |
|---|---|
| Build host configuration tooling | No |
| Maven build tooling | No |
| Container image build tooling | Yes |
| Docker-Compose deployment examples | Yes |
| Provision CI infrastructure | No |
| Provision deployment infrastructure | No |
| Container orchestrator | No |
| Application deployment automation | No |
The Self-Managed Commerce build tools supersede the Elastic Path Docker Project. The Elastic Path Docker project is available at Elastic Path Docker repository. For information about accessing this Git repository, see Hosting the Self-Managed Commerce Source Code.
Infrastructure suitable for running containerized enterprise applications can be used to run Self-Managed Commerce containers built by these tools. For more information about configuring and running Self-Managed Commerce containers, see Containerization.
CloudOps for Kubernetes
CloudOps for Kubernetes is a set of tools to provision and configure a Kubernetes cluster using Amazon Elastic Kubernetes Service (EKS). The resulting Kubernetes cluster contains tools to build and test Self-Managed Commerce code, tools to deploy Self-Managed Commerce applications, and tools to run those applications in a secure, scalable and resilient manner. CloudOps for Kubernetes supports and requires Amazon Web Services (AWS).
| DevOps Feature | Is it provided by this tool? |
|---|---|
| Build host configuration tooling | Yes |
| Maven build tooling | Yes |
| Container image build tooling | Yes |
| Docker-Compose deployment examples | Yes |
| Provision CI infrastructure | Yes |
| Provision deployment infrastructure | Yes |
| Container orchestrator | Yes |
| Application deployment automation | Yes |
CloudOps for Kubernetes uses a very specific architecture with a prescribed set of third-party tools and technologies.
There are advantages and disadvantages of using CloudOps for Kubernetes for your infrastructure. The main advantage is that it can allow you to have infrastructure up and running relatively quickly, provided you are willing to accept the architecture and technology choices inherent in the tooling. Disadvantages include:
- There is a steep learning curve.
- The technologies, solutions and architecture are prescribed for you.
- You must regularly upgrade as described in CloudOps for Kubernetes Support Lifecycle.
Some Self-Managed Commerce customers find that CloudOps for Kubernetes sufficiently aligns with their goals and requirements, and they are able to commit to the requirements of using it. Other customers find that it does not sufficiently align with their goals or technology strategies and they choose to implement their own bespoke solution.
For more information, see the CloudOps for Kubernetes documentation.