Event driven HATEOAS for ALT Service Mesh

Service Mesh

Event driven architecture

Event driven HATEOAS for ALT Service Mesh

  1. Forwarding addresses to new endpoints that expose new capability within applications.
  2. A service discovery like interface to list services for an api and discover new ones.

Lets look at an example:


  1. Any bank can be onboarded at any time.
  2. Any banking service can be added any time.
  3. Banks can move to new domains anytime and introduce new services into the system anytime.
  4. We can do a one time auth on the orchestrator to authenticate the user across the disparate banking apps.
  5. The customer can easily check what services are available and invoke the service for the correct bank by just providing Auth info, account id, action and amount one time, thus saving time.
  6. Disaster recovery is real time as Bank 1 simply needs to update the urls to its DR sites.




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

Recommended from Medium

Schedule messages in Slack: The best apps and options

Bringing DevOps to the Mainframe (2/4): Tooling

How To Become A Web3 Developer This Year

A man with curly hair standing while holding and reading a glowing book

Capture data from Kaggle to GCP

How to make C++ DLL and use it in Unity

Your Guide to Kubernetes Deployments

It’s not done if it’s not shipped

The start of a conversation…

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
Ritesh Shergill

Ritesh Shergill

More from Medium

What is a “Camunda Champion”

Versioning is eating the software architecture

SHA256.HashData Thread Safe

Creating a Context for School Board Decisions