Skip to content

Repository files navigation

Event Flow Design

  • The Patient Service acts as the primary event producer.
  • Billing and Analytics services consume events from Kafka.
  • gRPC is used for synchronous communication between Patient and Billing services.
  • Kafka enables asynchronous, event-driven communication for scalability and loose coupling.
  • Each microservice maintains its own database (Database-per-Service pattern).

About

An event-driven, cloud-native healthcare platform featuring spring-boot, microservices, API Gateway, Kafka messaging, gRPC communication, and containerized deployment.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages