mardi 16 octobre 2018

How to keep monolithic system up & running even when one of the components is not working?

I am currently working on very big (monolithic) web application. We often run into a problem when one of the modules/library/component encounters some problem as one module can stall the entire application. To solve this, everyone now a days suggests to go microservices way.

But I would like to know how the similar problems were handled "before" Microservices emerged as an option? And even if we decide to go Microservices way, that will be a long journey. How can we handle this problem during the transition period?

Aucun commentaire:

Enregistrer un commentaire