We will start with a rather short introduction in kubernetes, create a namespace using the MayopeCloudConsole. Using this namespace we will deploy a docker container and make it accessible from the internet. What can I do with kubernetes? Kubernetes is a tool to orchestrate containers. It enables you to run, configure, scale and connect them against each other. How does kubernetes archive this? Kubernetes can be understood as a tool to connect multiple (physical or virtual) machines and enable them to share workloads.
Documentation as Code makes it first class citizen while developing Documentation as code states that you store the documentation of your project/service at the same location where you store you code. This has some clear advantages: You don’t need to search for you documentation, everybody is aware where it is and how to extend it You can update the documentation for an issue in the same pull/merge-request where you make the respective technical changes.
Why do we need monorepositories in the first place? This article does a great job in explaining what a monorepo is and why you may need it: What is a monorepo? To summarize it you have a couple of advantages: Single source of truth Pull-Requests accross services are possible and reviewable in one pull request Simplified code sharing accross services Common build logic for all services There are also some downsides for using a monorepository for example vsc scalability, cross team ownership or the temptation to introduce tight coupling between services.