This is what is great about microservices! We can replace a single service with another language without worrying about other parts of the platform. We are likely going to change the programming language of some services. This is partly because we started with Node.js, but also because Node.js allows asynchronous processing of webhooks, tasks and more. Currently, a lot of Lagoon is built in Node.js. We try to decide which language makes the most sense for each service. Each programming language has specific strengths. Lagoon uses many programming languages.It also allows us to try out new parts of Lagoon in production without affecting others. It allows us to survive down times of individual services. Microservices communicate through a messaging system, which allows us to scale individual services up and down. It's built with flexibility and robustness in mind. Each deployment is unique and can take from seconds to hours. We have multiple version control sources, multiple OpenShift servers, and multiple notification systems. The deployment and build workflow is very complex. Head to #lagoon in the amazee.io RocketChat: A couple of things about Lagoon # Questions? Ideas? Meet the maintainers and contributors. When all is done, Lagoon informs the developers in different ways (Slack, email, website, etc.).Lagoon monitors the deployment of the containers.Lagoon creates the needed resources in Kubernetes.Lagoon pushes them to a Docker registry.Lagoon builds the needed Docker images.
Lagoon parses the YAML files and adds in any additional needed configuration.