How kbastani/cloud-native-microservice-strangler-example works
Project type and purpose
• This is a reference implementation of the Cloud-Native Strangler Pattern using Spring Cloud microservices.
• It demonstrates how to introduce microservices into an existing SOA/legacy architecture, “strangling” monolithic data access over time.
• Key use cases:
– Legacy application integration (Customer Service, Legacy Edge)
– New cloud-native microservices (Config, Discovery, Edge/Gateway, User, Profile, Profile-Web, Hystrix Dashboard, Zipkin tracing)
– OAuth2 authentication, service discovery, circuit breakers, API gateway, distributed tracing.
File structure
Top-level directories
• legacy-applications
– customer-service: a SOAP/REST legacy WSDL-backed Customer service
– legacy-edge: a legacy gateway adapter routing calls to new services
• microservices
– config-service: Spring Cloud Config Server
– discovery-service: Eureka service registry
– edge-service: Zuul API gateway / proxy
– hystrix-dashboard: Hystrix monitoring UI
– zipkin-tracing: Zipkin server for distributed tracing
– user-service: OAuth2 authorization/resource server + user domain
– profile-service: profile/domain microservice, listens for legacy data events
– profile-web: Angular-based UI for profile
• root scripts/config
– docker-compose.yml, run.sh (Docker Compose orchestration)
– deploy.sh (Cloud Foundry deployment)
README for additional insights
• The README outlines a hybrid legacy + microservices architecture, highlighting the Strangler pattern, lazy data migration, durable event mirroring, and Spring Cloud Netflix components.
Detail
– Capture every Spring Boot application, its role, and dependencies.
– Show inter-service communication and fallback paths (Hystrix).
– Don’t over-aggregate: represent each microservice as its own node.