Developing Microservice Project(Doctor-Appoinment) Using Spring-boot [Secured] using OAuth2
- Admission
- Doctor
- Patient (Resource Server)
- Why Micro-service?
- Why API-Gateway needed?
- Fine, But why config-server?
- Is it necessery to use Hystrix Dashboard?
- Is it secured?
- Eureka
- Gateway
- Hystrix
- Hystrix-Dashboard
- API (resources)
- Config Server
- Authorization server and Resource server
- Appointment UI
***Perdon me for mistakes(if any)
- Start Eureka-Boss Service
- Then Config-Server, Gateway service
- Then Admission,Doctor,Patient, Hystrix-Dashboard
- LoadBalanced (Implemented before ResTemplate, also in Gateway .yml file [lb] )
- Try to access: http://localhost:8989/admission/allDoctors (8989 for Gateway, URI for accessing Doctors from Admission)
- Dynamic CircuitBreaker pattern added for Admission (as it has Internal API call), also exposed actuator End-point for Hystrix-Dashboard
- For Dashboard: http://localhost:9191/hystrix , then copy target URI (http://localhost:8083/actuator/hystrix.stream) and Hit Monitor Button
- Change EndPoint, Values without making any changes in code..Cool
- No need to repeat same Config for all resources over micro-services
- Remember (add a repo, add dependencies, point to config-server uri in bootstrap.yml file)
- @Value for reading value from Config-server