Hands-On Microservices with Kubernetes

Monorepo

In the monorepo approach, your entire code base is in a single source control repository. It is very easy to perform operations over the entire code base. Whenever you make a change, it is reflected immediately in your entire code base. Versioning is pretty much off the table. That's great for keeping all your code in sync. But, if you do need to upgrade some parts of your systems incrementally, you'll need to come up with workarounds, such as creating a separate copy with your new changes. Also, the fact that your source code is always in sync doesn't mean that your deployed services are all using the latest version. If you always deploy all your services at once, you're pretty much building a monolith. Note that you may still have ...