Chapter 2: The Microservice Architecture

It has been a long time since my first post of this series. However, now I have lots of changes that are set and defined. In this post, we will discuss the architecture and the data model.

In the last post, I stated the main guidelines of the Master Thesis, the development and deployment of an e-commerce platform on a Cloud Microservice Architecture. After more than 2 months, we have defined the main requirements of the platform and a first approach to the architecture and the data layer. Also, the first fully functional version is expected to be finished next July 2021 only with the happy path.

This first analysis has resulted in between 17 and 19 microservices across the 9 domains, not taking into account the frontend and back office of the application. Each domain also has at least one persistent storage unit, which is either a database (relational or NoSQL) or an ElasticSearch pod. These last days, I also finished the design of all entities each domain is responsible for.

Next steps
After this second milestone, the next steps will be generating a dummy project for each microservice with the needed libraries to represent the data model and deploy all of them in the 2-node Kubernetes Cluster.

What is “Diary of a Master Thesis”?
Starting December 2020, I decided to collect in a series of posts on LinkedIn my progress in the Master Thesis that is supposed to be defended in September 2022.