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

Micro Services are not a Silver Bullet

“If you can’t build a monolith, what makes you think microservices are the answer?” – Simon Brown

Continuer la lecture de Micro Services are not a Silver Bullet

Micro Services – Reasons For Partitioning?

A few posts back we spoke about how Microservices affect organizational structure and how the structure of an organization mirrors the structure of its architecture. By structure of an architecture we basically mean partitioning of that architecture and hence the organization.

Continuer la lecture de Micro Services – Reasons For Partitioning?

4 great videos to watch on Micro Services

1. Practice Considerations for Micro Services Architecture

By Sam Newman, tech consultant @ ThoughtWorks

Screen Shot 2015-07-07 at 15.59.38

 

Continuer la lecture de 4 great videos to watch on Micro Services