 There are different architectures, a version control and collaboration system can support. In this case, this is an example of a microservice architecture. This e-learning company with a website built with front-end technologies and a chatbot that takes questions and payments from customers reading different backends. The chatbot and website were built using totally different technologies, skills and development teams, and here these two channels peacefully coexist and drive a single customer experience. My name is William, and let's learn today how GitLab can help us bring to life a microservices architecture. The business side from this company has created this domain view of the e-learning platform. It is a good starting point. From here, a technical architect can take it and design a system with microservices philosophy in mind. For the chatbot interaction we saw, this will be the result. The chatbot itself is a self-contained service that has to interact with other independent systems to achieve its goal of providing information and course enrollment to the customers. So how can I enable the company teams, business and developers to work together fueling this system design? In GitLab, I can create groups and projects to reflect on that business domain segmentation that the business side gave us before. Seems familiar? We have translated the business domain segmentation to subgroups and projects. Let's check under this structure some advantages of this architecture implemented on GitLab. The business team wants to add one more answer to the chatbot knowledge base because the FAQ is modeled as an independent service in GitLab. Under this project, it is possible to have FAQ-related issues only, start a merge request and add the new question to the knowledge base. Here, I create and describe the issue with the answer I want to add. Now I assign it and submit the issue. From here, I want to work on the changes. So I will create a merge request and then I open it up on the web IDE. By the way, this is a dark theme. Under this project, I click on data folder. At the question describing the issue, it only takes a simple JSON edit. And finally, click on commit. I have GitLab CI configured. So once I commit and the changes are validated and everything comes back clean, where by the way, one of the steps was to validate the JSON data integrity. Then I am ready to merge it to production. All right, we successfully updated and tested the FAQ microservice. Let's see it on action. Cool, it works, as expected. Because as we could see by implementing microservices architecture in GitLab, I can test and maintain the project independently. We learned today how to use GitLab to translate a system and microservice architecture design into actionable parts with groups and code projects. We saw how different parts of the platform can be independently created, maintained and tested, ensuring that when we tie them together, we will build bigger and robust solutions. But wait, wait a second. What if I need another application architecture? You better stay tuned and let's continue learning at GitLab.