I have some questions about creating microservices with Django. Let's say we have an online shop or a larger system with many database requests and users. I want to practice and simulate a simple microservice to learn something new. We want to create a microservices-based system with the following components: A Django-based microservice with its admin panel and full functionality (excluding DRF). One or more microservices with a React/Angular frontend. Several additional microservices to separate functionalities. I'm unsure about the architecture. Let's assume we want to manage data using the Django admin panel. The simplest solution would be to add DRF to the first microservice and extend its functionality (REST app) - instead of creating different services (3.). But what if we want to separate functionality into different microservices? Should the microservices in point 3 be connected to the same database and treated as different Django projects (with DRF)? Can we use GoLang, FastAPI, or Java Spring for the third microservice? If yes, should all models be duplicated and registered in the first microservice? Alternatively, is there a better way to approach this? It would be great to hear your perspective and methods on how to proceed with this. Have a wonderful day! Continue reading...
