Rupesh
This is regarding best practices for microservices version controlling (Github)
Could you please go through the below description and help me in clarifying my doubts?
I am developing a simple Library management system using Spring boot and spring cloud. We will have 3 simple spring boot-microservices
a) User service (https://github.com/rupeshpa… Book Service (https://github.com/rupeshpa… Library Service (https://github.com/rupeshpa…
Additionally, will have spring cloud services like config server, naming server, API gateway, etc.
Ask 1) What should be repositories structure or setup? I mean should I create a separate repo for each service like did for the above 3 services but personally feel a bad idea to have multiple repos (considering repo limit for an account or budget issue)
Ask 2) If we go ahead with a multi-module project, we can have a separate module for the above 3 microservices and can also have modules for API gateway and eureka server. And a completely new repo for the config server as it will be shared with all modules. Will this be good practice and how it’s easy to scale or maintain in the future?
Ask 3) Considering the future scope of moving to serverless architecture, which practice would be easy to migrate to serverless or to Kubernetes?
Appreciate any help.