Yazid
For others who would have the same problem, it can happen if you didn’t set the Okta credentials in both services: api-gateway and car-service. Just make sure you have properly set the values of okta.oauth2.issuer, okta.oauth2.client-id and okta.oauth2.client-secret in the application.properties in both services.
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.
Matt Raible
I think it’s important to be able to release your microservices independently. It seems like a repo for each service would make this easier to do than having a monorepo with all services in it. If you have teams of 10 that develop and maintain each microservice, I don’t think this is too much.
However, if you have a 1-2 people that maintain each microservice, then maybe you’re using microservices for the wrong reason. In my experience, microservices are excellent for scaling up developers and might not be needed if you’re just trying to scale up your technology stack. Some of the highest-performing systems I’ve worked with in my career have been monoliths.
williamhudson
Hi @Matt Raible:disqus its a Nice artcle i am IOS and Android developer @ SpotnRides ,Its a nice article about the java programming i would like to learn more from it