❔ How to properly design microservice architecture in ASP Net Core?
Hello everyone. It's going to be my first try to follow microservice architecture pattern. I have read lots of articles on the web but still have a few doubts and questions about this topic. I'm wondering how should I design the project in ASP Net Core. Especially:
1. should I create multiple services under one solution?
2. should I create a new solution for each service?
3. should I create API Gateway as an app in seperate solution or under existing solution (e.g. along with one of the services)?
4. should I always containerize microservices or not?
5. is it possible to deploy microservices apps without containerization?
6. I have one server with one database where all data is stored. I read that each service should have its own database. Can I use one database for each service (but each service will be using different tables , not share the same tables)?
7. does it make sense to create seperate service where all required data from database/s is stored (e.g. data from a few servers)? And then other services (e.g. Payments, Products, Clients etc.) would communicate with this data service to make CRUD operations? Normally, each service should have its own database but what about this approach?
Thank you for your answers
1. should I create multiple services under one solution?
2. should I create a new solution for each service?
3. should I create API Gateway as an app in seperate solution or under existing solution (e.g. along with one of the services)?
4. should I always containerize microservices or not?
5. is it possible to deploy microservices apps without containerization?
6. I have one server with one database where all data is stored. I read that each service should have its own database. Can I use one database for each service (but each service will be using different tables , not share the same tables)?
7. does it make sense to create seperate service where all required data from database/s is stored (e.g. data from a few servers)? And then other services (e.g. Payments, Products, Clients etc.) would communicate with this data service to make CRUD operations? Normally, each service should have its own database but what about this approach?
Thank you for your answers
