Collaboration when developing Spring Boot Microservices
summary
Problem: running dozens of Spring Boot microservices locally causes resource strain or central environments cause request collisions. Uses Spring Cloud with Eureka for discovery and Zuul (or Spring Cloud Gateway) for routing. Each local service registers as <hostname>.<service> via an Eureka bean renames service to host.service, and a gateway filter checks caller host and requested service and performs gateway rewrites route to host.service so requests from that developer go to the local instance while others hit the central ones. Demonstrated working in a live demo.
AI-written summary · about
chapters (4)
- 0:00Start
- 8:30Spring Cloud - A Quick Intro Tools/Frameworks for distributed apps (not just cloud!) • Introduced in 2014 . 33 items in the spring cloud docs! Examples: distributed locks, configuration, circuit breakers, load balancing, and many more...
- 13:50The problem... - The number of micro services went up . For developers to develop and test ſintegration , should they - Run everything locally? • Run only one service locally and the rest on
- 21:20Work with the global discovery (to find central services) • Local services would register under a different and unique name in the global discovery • E9. Payment-my-machine. Payment • Smarter Gateway (Extend Zuul): . If the request to service X comes from my machine, and there's my-machine X- Route to my machine
related talks
01h 03mThe Bootiful Microservice
53mBooting your micro-services architecture with Spring and Netflix
29mSpring Boot Microservices Architecture: A Deep Dive
53mScaling Spring Boot Microservices
51mBrewing the Best of All Worlds
46mDivide and Conquer Send Forth the Microservices
51mIntroducing Spring Cloud Gateway
53mThe Beginner’s Guide To Spring Cloud