From having their deployment in Heroku, they Cliengo approached DinoCloud to perform a migration to AWS, thus achieving a magnificent improvement in their performance.
Cliengo is a company founded in 2017 dedicated to driving business relationships by helping other businesses convert users into customers and helping scale their own customers’ business processes by automating all contact channels.
Businesses that engage Cliengo can deliver their customers a supreme experience with 24/7 open channels. They integrate with the technologies that these businesses already use and generate reports that allow them to optimize omnichannel customer service.
When Cliengo approached DinoCloud, they faced the primary challenge of migrating from Heroku to Amazon Web Services. Additionally, they needed to build continuous integration and continuous delivery pipelines. Another critical challenge was containerizing their microservices, which were developed in various frameworks (Java Play, Node, PHP). Finally, they sought to identify the specific microservice causing a bottleneck, a significant task given the number of microservices in use across their platform.
Stages, technologies, and services implemented
Our process with Cliengo began with a thorough discovery phase. We analyzed their existing setup in detail, which led us to create a comprehensive diagram for visualizing their infrastructure.
With this insight, we proceeded to plan and organize the necessary tasks, or epics, which included:
Simultaneously, we began migrating Cliengo’s platform from Heroku to Amazon Web Services (AWS) with Kubernetes. This initial phase required us to dockerize their applications and build a Kubernetes cluster using Terraform.
After setting up the cluster, we ensured the configuration was optimal to support seamless operation. We then created Kubernetes manifests for each microservice, identifying and implementing any that were missing during discovery.
Once the platform was verified to be fully operational, we deployed automation pipelines using GitHub Actions, customizing them to align with Cliengo’s specific needs.
At DinoCloud, we specialize in transforming a company’s current infrastructure into a modern, scalable, high-performance, and cost-effective system designed to meet business objectives. If you’re interested in optimizing your data management, enhancing analytics, and reducing costs, feel free to contact us here.
Cliengo faced a challenge where multiple teams were working on applications associated with each microservice. This setup led to issues during deployment, as teams would frequently encounter conflicts due to the previous team’s work on the same complex codebase. Without a structured branching strategy, project efforts became inconsistent, resulting in costly and time-consuming errors.
To address this, the DinoCloud team collaborated with Cliengo to implement an effective branching strategy through their deployment pipelines. This approach allowed Cliengo to create pull requests that would deploy into a separate namespace within the same Kubernetes cluster. This setup enabled teams to test new features without affecting the overall development environment or other microservices.
Once a feature was tested, it could be merged seamlessly into the main development environment, significantly reducing error rates and enabling each team to run tests within the cluster without impacting others.
The results are summarized in obtaining a Kubernetes cluster in AWS 100% functional, it is important to note that it was also possible to dockerize all the microservices without major problems, with the operation of all its corresponding pipelines and with a branching strategy, which managed to greatly meet the expectations of Cliengo, implemented.
An inconsistency could also be evidenced through New Relic and an automation Workload. Last but not least, a migration from Heroku to Amazon Web Services in a developed space was performed.
Focus on your core business while DinoCloud provides the
technology outcomes you need by leveraging its expertise in
the cloud.
(*) Required fields
