Having a reliable system that can process orders coming through worldwide retail branches of the store for international clients is a must-have. With around 4 mln users monthly, the B2C online store needs some enhancements in its operating e-commerce platform.
- Operate the increasing number of apps and use fewer VMs’ power
- Isolated application launch in containers to save space
- Development, testing, and app deployment requires more simplicity
Kubernetes on top of Docker containers solves all of these issues and many more. Often retailers address us with rapid business growth where fast system scalability is on demand.
Recently, we tried to move Hybris into Docker containers with K8s over it. Running a 6.5 version on Kubernetes in cluster mode we faced the issue that PODs couldn’t see each other.
It was crucial for the client to simplify apps scalability and handle their operation with a container orchestration system.
So, the Hybris configuration cluster mode “on” and “cluster id” was generated automatically. We could ping “first” pod from “second” manually, in a reverse way also. But for some reason “physical address” defined as localhost:
We tried and found two ways to do it:
- Hybris side: we need to extend a startup wrapper with the following variable:
- Kubernetes side: we need to extend a YAML config file with the following container spec:
Opting for Kubernetes rather than AWS for an enterprise e-commerce platform, we’ve got several advantages.
- Kubernetes is quite flexible in resource consumption management.
- Automated restart after emergency stop caused by overconsumption of resources.
- No need to configure the launch environment; it comes with an application in the container.
- Easy apps deployment and operation in a microservice architecture.
- You can easily migrate app instances between hosts to prevent breakdown and ensure stable operation.
Well, concerning Kubernetes it’s all about easiness and automation. Please, share your cases if experiencing it. It seems to be nice to contribute to this topic.