Adapter Pattern for Microservices

Scenario:

  1. Load call to Data Source A Service.
  2. Data Source A Subscriber
  • Data source A is using Kafka for event publishing while Data source B is using RabbitMQ.
  • Data source A is using REST API but Data source B is using GraphQL API.

Solution

  • The core domain services doesn’t have to change when there is any change in Data Source A service, Data Source B service etc.
  • The core domain services doesn’t have to host any translation logic. The developers can focus on core concepts.
  • The core domain services doesn’t have to worry about the “technology” methods being used by Data Source A service, Data Source Service B etc.

External References

--

--

--

Software Architect

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

3-way merge in werf: deploying to Kubernetes via Helm “on steroids”

How to Validate a CSV in C/C++

Encode x NEAR: Intro to Blockchain [Video + Slides]

Reminder: Your Skype for Business Online apps will NOT work in Microsoft Teams (act before July…

Impressions from the first weeks of the Ambassadorhood 🤩

10 Best Open Source Mobile App Development Software in 2022

Is It Possible to Back Up Both Mac and Windows Systems to the Same External Hard Drive?

Protocol Buffers & gRPC

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Atul Agrawal

Atul Agrawal

Software Architect

More from Medium

Microservice — The visualization problem

Decomposing monolith into microservices

Domain driven design eCommerce

Part 3: A comparison of CRUD and CQRS patterns using shopping cart application