Hey, and welcome back to our series on EC's methodology. Last time we talked about services you might need for your application. Today, we'll talk about coordinating all of those services. Your services are an orchestra and it needs a conductor. Okay. So we've got all of these services. And we know they need some way to talk to each other. So, how do we do that? Everything we build gets turned into a container, a way of packaging applications that was popularized by a tool called Docker.
So when we're developing, we recommend using a tool called docker-compose to run and coordinate those services. Though, we're also exploring an alternative called pod man. Now let's talk about getting all of those services up and running in a production environment. Until a couple of years ago, we probably would have spun up a bunch of virtual machines in auto scaling groups on AWS. In some cases we might still do that.
But since the explosive growth of Kubernetes an open source platform designed to orchestrate containerized workloads, we find that to be a much better way of deploying and managing our services. It has pros and cons, but one of the advantages of Kubernetes is it's an open source system with managed offerings on most cloud platforms, including Google, Amazon, Microsoft, Digital Ocean, and others.
So, if you build for Kubernetes, you should be able to pick and choose the cloud that best suits your needs. Tell us about how you manage and deploy your services. And follow us if you want to keep up with this series. We have a lot more to share with you. We're constantly updating this process. As we learn from ourselves, our partners and our community. If you think we could work together, we'd love to partner with you and help you out with your next project. Thanks and see you next time.