Fundamental traits of Micro Services

Micro Services work best when deployed in groups. Their numbers make them a complete system and today we will touch upon the underlying fundamental traits that make it possible for them to work the way they do. Continuer la lecture de Fundamental traits of Micro Services

What comes first? Micro Services or Micro Segmentation?

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?

Micro Services – Code Small Enough To Remove

As a general rule the delivery rate of all commissioned software is pretty low when we take into account the total amount that are commissioned versus the amount that are actually accepted and used by a somebody. Over that when it comes to business software in particular the average life is about 5 years before it becomes obsolete – dead!

Continuer la lecture de Micro Services – Code Small Enough To Remove

Nous aimons l’échec

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

Micro Services – A Case for the Sidecar

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