paint-brush
How to Avoid Inconsistency Across Microservicesby@skogorev
327 reads
327 reads

How to Avoid Inconsistency Across Microservices

by Anton Skogorev3mOctober 6th, 2022
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

In a distributed microservice architecture, you can get dependencies that impose restrictions on the services used. In order to remove a geoarea from a microservice, you need to make a request to `Tariffs` at the time of removal to check which tariff depends on it. This can lead to the inaccessibility of the service since we still have tariffs referencing a removed geoarea. There are several solutions: Webhooks, reference counting, and reference counting. When a new microservice that uses*Geoareas* appears, add a new check to the list of hooks.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - How to Avoid Inconsistency Across Microservices
Anton Skogorev HackerNoon profile picture
Anton Skogorev

Anton Skogorev

@skogorev

Head of backend development at Yandex Taxi Marketplace Efficiency department

L O A D I N G
. . . comments & more!

About Author

Anton Skogorev HackerNoon profile picture
Anton Skogorev@skogorev
Head of backend development at Yandex Taxi Marketplace Efficiency department

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite