It reads like the chicken and egg story only in the case of Micro Services and Micro Segmentation it is very easy to think that they come as a package deal and thus confuse the two. Continuer la lecture de What comes first? Micro Services or Micro Segmentation?
A good house is built on a strong foundation. The same holds true for systems architecture. How you build your Micro Services determines what they turn into.
While there are many ways you can choose to build your Micro Services, all of them can broadly be divided into 3 categories. Continuer la lecture de Three architectural strategies for Micro Services APIs
Echouer est le meilleur moyen de réussir. Notre choix d’architecture reflète cette philosophie.
Dans tout service il y a des erreurs. Qu’il soit monolithique ou construit à l’aide de micro services, il peut tomber en panne à tout moment. Le travail d’un éditeur est de détecter ces erreurs et les réparer rapidement. Continuer la lecture de Nous aimons l’échec
One of the most fascinating traits of Micro Services is that they are polyglot or as we like to say here at Captain Dash – they are a Google translate that works.
There are obvious advantages of such an architecture, the biggest being that we can use the best tool for getting a job done. Continuer la lecture de Micro Services – A Case for the Sidecar
“If you can’t build a monolith, what makes you think microservices are the answer?” – Simon Brown