3 years ago

Category: Laravel, MySQL

Now that our setup is done, and the foundation for a scalable architecture is ready, we can move forward and think more deeply about the design that we want for our entire system. We will try to setup the guidelines to follow whenever we have to create and to implement the existent or new micro-services, because we could eventually still have to spawn a few other micro-services every now and then in the future, on demand depending on the needs of the design we will opt for, and make some DevOps adjustments to make sure that all pieces are working properly together. At the same time, it is important to mention that overall, the boring part of the setup is behind us from now on ward and we are getting closer to the funniest part. As we definite since the beginning of this series, the main purpose of these articles is to introduce the Micro-service Architecture at first, then to provide a step by step demonstration of how to design and implement it.While there is no precise definition of this software architectural style, there are certain common characteristics around the scalability, continuous integration, automated deployment, intelligence in the endpoints, decoupled business logic, language agnostic components and decentralized control of data.Since we are in an educational process, it is obvious that we won’t be able to cover all these aspects listed above, specially those that are related to real live production processes, such as CICD (Continuous Integration / Continuous Deployment), in the other hand we will try to have a clear overview of all the facets that are important from a design perspective. For learning purposes, we will be creating a Minimum Viable Product of an ERP (Enterprise Resource Planning) system that manages the product’s inventory of an e-commerce company, and in order to make the process as smooth and straightforward as possible, we will be doing some abstraction and avoid to dig deep into ERP’s business logic.