How efficient is your development now?
90 days? How is this possible?
We have refined our method so that it’s a reliable, step-by-step process!
The migration is done with zero downtime and almost no time lost from your development schedule.
During the migration process we’ll:
Leonid’s calm and professional approach to problems is inspiring. He manages to concentrate on the results instead of being distracted by the daily noise. His approach helped us launch the product on time and made our developers happy working with…read more→
We knew we needed to improve our build and deployment process, but we lacked the needed resources. Leonid helped us transition to Kubernetes which revolutionized how we deploy our software. During our work together Leonid was always available for support…read more→
Before working with Leonid, we had stability issues in our deployment and build automation -- we weren’t sure that each deployment would succeed. Leonid helped us solve our deployment problems by cleanly migrating our environment to Docker and Kubernetes. He…read more→
What will happen after the migration? Will we need you for ongoing, day-to-day operations?
No. After setup, your team will be able to operate the system autonomously.
We include the training session toward the end of the project so your team knows how to do it all themselves. It’s important that your team gets very comfortable with Kubernetes to gain the full productivity benefits that these tools offer.
We don’t have the budget for a consultant. Won’t it be better to hire a full-time employee?
If you can wait for 3-8 months until you’ll find the right candidate, hiring a full-time employee can be a better option.
Usually, it’s harder for young startups with relatively small teams and scale to attract senior level DevOps engineers. For a price of a few months’ salary, you can migrate your whole stack to Kubernetes within a few months and revisit the idea of hiring another team member when your development team is bigger.
When is the ideal time to schedule this migration?
If one of your development team members spends around 40%-70% of his time on debugging failed builds or maintaining existing cloud infrastructure, you have probably already reached the point when standardizing your infrastructure by migrating to Kubernetes makes a lot of sense.
How big should our dev team be to get maximum benefit from this service?
From my past experience working with clients on similar migrations, usually development teams of 10-30 people get the most benefit from this service.
If we can fit the whole team in one room for a Kubernetes training, it’s a good sign that your team is a perfect size for making this technological change relatively quickly.
That said, even with teams of that size, we usually work with a small subset of team members who are our contact points in the organization and lead the change together with us.
Do we need to prepare anything on our end? How much change will our developers need to make to their workflow?
If you already have automated test and build processes using Jenkins or any other CI service, we’ll make sure to integrate Kubernetes into the same pipeline so your developers won’t need to learn a new workflow for deploying their applications.
Toward the end of the project, we’ll hold a hands-on training session to help everyone feel comfortable with managing their applications in Kubernetes. Although for the day-to-day operations the team won’t need to work with Kubernetes directly, it’s still important to get everyone comfortable with Kubernetes’ CLI so that the team will be able to add new microservices to the platform with ease or respond faster in case of a service interruption.