Codevops Solutions

01/25/2022

The One And Only Heroku-to-AWS migration calculator. https://bit.ly/3fSlLiC Estimate your savings with no commitments!

01/20/2022

01/18/2022

General Availability of AWS Local Zones in Atlanta, Phoenix, and Seattle. Ask for migration support https://bit.ly/34QOB0w

01/14/2022

Rolli migration from Heroku to AWS
Rolli is a platform where media producers can find experts in a field. They help instantly search the leading database of qualified experts and find the one that best suits your segment or story. All experts have been thoroughly vetted based on credentials, expertise, and professional affiliations, so you can book with confidence.

The Business Challenge: Rolli needed a specific DevOps solution and wanted to change its cloud architecture after successfully launching, and migrating from Heroku to AWS. Even though Heroku was a good choice when releasing the product, as the team started scaling it and more users were using it, this choice became expensive. Besides that, after it started getting more traction, infrastructure security became an issue. The fact that the company couldn’t own the servers wasn’t something that the company could move forward with. Therefore it was necessary to move to a cloud provider where the team could own the servers fully.

Setting up AWS Environment: The AWS infrastructure and accounts have three primary requirements:

- Complete DevOps Automation;

- Provide access only to a few specific people to manage it;

- Allow anyone with privileges to deploy an application's new version with a single click.

The Application Architecture: The application was a Ruby on Rails 5.2 monolith. The goal was to just move as it was to AWS and have multiple instances accessing the same database. It was a straightforward scenario. Data would be moved from Heroku’s Postgres to AWS RDS, which was done by a simple data copy in moments of low traffic. The team was using Docker for development only but wanted to start using it in production as well.

Automation: Rolli’s Github account hosts the code repository and the team was using Github Actions to automate the tasks.

Conclusion: The final result is a flexible and automated infrastructure that securely executes applications. In comparison to Heroku, the prices are 25-27% lower than first projected due to the on-demand nature of Lambda and the utilization of ECS's auto-scaling features. The move to AWS also enabled the Rolli team to optimize the application code, lowering expenses even more (up to 50% actually). However, we believe that the openness and trust shown to us by the Rolli team was the decisive element in the success of this project. Ultimately, this resulted in outstanding cooperation, for which we are grateful.

01/13/2022

The https://codevops.io is live now. Find the unique Heroku to AWS migration cost calculator there.

01/12/2022

Kubernetes Deployment

Everyone running applications on Kubernetes cluster uses a deployment. It’s what you use to scale, roll out, and roll back versions of your applications. With a deployment, you tell Kubernetes how many copies of a Pod you want running. The deployment takes care of everything else.

What is a Deployment?

A deployment is an object in Kubernetes that lets you manage a set of identical pods. Without a deployment, you’d need to create, update, and delete a bunch of pods manually. With a deployment, you declare a single object in a YAML file. This object is responsible for creating the pods, making sure they stay up to date, and ensuring there are enough of them running You can also easily autoscale your applications using a Kubernetes deployment.

Deployment vs service

What’s the difference between a deployment and a service?
A deployment is used to keep a set of pods running by creating pods from a template. A service is used to allow network access to a set of pods. Both services and deployments choose which pods they operate on using labels and label selectors. This is where the overlap is. You can use deployments independent of services. You can use services independent of deployments. They just go together really nicely!

This lets you do canary deployments. You add a new deployment version of a pod and run it alongside your existing deployment, but have both deployments handle requests to the service. Once deployed, you can verify the new deployment on a small proportion of the service's traffic, and gradually scale up the new deployment while decreasing the old one.

01/04/2022

tools are always ready to support your deployment pipelines. Check this out!

12/22/2021

12/22/2021

Migrating to AWS opens up a whole new world of functionality and flexibility for your application, allowing you to scale both vertically and horizontally as needed. If you’re looking for an experienced partner in the migration process, CODEVOPS has the experience necessary to help make sure that your application is ready for prime time on AWS from day one.

12/20/2021

Need more from DevOps? https://codevops.io
Modern software development is all about customization. Customized methodologies that enable development and delivery have essentially overtaken the unified feature-rich model of conventional waterfall development. Customized deployment has changed the character and power of software development in unexpected ways. As the process of customization evolves, it incorporates continuous integration, continuous delivery, and continuous deployment.