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.

La structure monolithique est complexe. Elle est par essence difficile à tester, déployer et maintenir.

Les micro services sont eux construits pour supporter ce type d’échecs. La pluralité des services minimise leur interdépendance. La panne de l’un ne fait pas tomber l'ensemble du système.

Une architecture de micro service est structurellement sous surveillance. On peut ainsi, comme le fait le programme Simian Army de Netflix, tester ses limites et l’améliorer infiniment.

L'écriture minimaliste du code, la vitesse de déploiement, la capacité à réparer et modifier chaque application individuellement nous donne la flexibilité nécessaire pour innover et tester aussi souvent que nous le voulons.

Cette flexibilité nous permet d'assumer l'échec. Et l'échec est la source vive de l'innovation. Nous pouvons innover, tester, nous tromper sans perturber l’ordre des choses.

Ne pas avoir peur de l’échec permet aux équipes de repousser les limites et les normes et de réaliser l’impossible.

C’est cette capacité à accepter l'échec qui nous fait aimer les micro services.

Note : Captain Dash commence une nouvelle série d’articles sur les Microservices. Certains sont techniques, d’autres moins. Notre objectif est de considérer cette forme d’architecture que nous utilisons et de la rendre compréhensible pour le commun des mortels. Ces articles seront publiés tous les dimanches. Donc suivez-les sur Twitter ou abonnez-vous à notre blog et recevez votre mise à jour hebdomadaire sur cette fabuleuse architecture qui est en train de changer la façon de faire des affaires !


Micro Services are not a Silver Bullet

if you can’t build a well-structured Monolith, what makes you think you can build a well-structured Micro Services system?

Read more

Micro Services Allow us to Innovate!

In our two last posts on Micro Services we have discussed anti-fragility and the ability of Micro Services to survive failure.

 Related to both these qualities is innovation. Micro Services facilitate innovation at a very fast pace, thus making it possible to not only be disruptive but also remain so.


A traditional Monolithic application does not give us much opportunity for innovation. Due to the way it is built, changing things and experimenting can be risky due to the fact that the changes potentially affect every aspect. Thus, any kind of innovation is limited.

 Micro Services, on the other hand, respond very well to changes. The decoupled nature of this structure makes it possible to change each individual service in any way that works best for that particular service. The fact that this is a polyglot architecture gives the designers the freedom to work in the language that works best for a particular aspect of the system. This is not to say that the languages have to be different for it to work but just that the options are available.

Another feature that helps to keep the innovation constant and fast paced is the size itself. A small set of code is definitely easier to change and mould as need be compared to a larger set of codes. Smaller services are also easier to test and deploy thus making it possible to innovate and change faster.

The size and modularity of Micro Services ensures that even if a particular change brings down the application the entire architecture is not affected by the failure. This feature, especially, is what gives the teams the confidence to experiment and play with ideas without the fear of a complete shut down.

Anti-fragility, the ability to survive failure and finally the freedom to innovate is why we, at Captain Dash, consider Micro Services to be our secret sauce. They make it possible for our team to offer innovative, completely customised solutions for our clients – solutions that work!

To stay updated with our series on Micro Services architecture follow us on twitter or subscribe to our blog.

Written By: Meghna Verma Meghna Verma is the Content Manager at Captain Dash.  You can reach her on Twitter @M3GV3RMa .

Anti-Fragile - Micro Services Love Stress

When it comes to architecture safety, we traditionally refer to systems as being fragile or robust. But, there is in fact a triad – Fragile, Robust and Anti-Fragile!

antifragile-microservices-and-devops-a-study-4-638Over the years, companies have invested millions in their architecture and with each passing addition these architectures grow increasingly complex till they are a mass of technological spaghetti. When faced with such architecture we are afraid to touch it with fear of completely unraveling it. This is what a fragile system looks like; a system where even the slightest change can result in a complete breakdown.

The solution routinely sold to us is to make it robust, more resilient. This solution consists of wrapping a fragile system in layer upon layer of protection – much like bubble wrapping a delicate wine glass – and these layers will need to eventually be removed to affect any changes. A robust system will at it’s best ignore changes and at it’s worst will resist change. This is dangerous in the present environment of constant change.

Micro Services offer us the third option – to build an anti-fragile system! An anti-fragile system simply put is a system that not only thrives but also benefits from stress – the stress of run time, of change, of failure. It gets better with stress and allows us to embrace change and agility.

An example is Netflix’s Simian Army. This is a tool that systematically destroys their existing system to expose weaknesses and forces the system to improve, to handle runtime conditions better and to change faster.


Imagine a system that allows you to destroy it and comes out of that better than before! THIS is what Micro Services bring. By allowing for mistakes, stresses, and weaknesses they lead us to take leaps in innovation instead of baby steps. We can call Micro Services just another name for SOAs or call them a buzzword but what they bring to the table – anti-fragility, flourishing on change, innovation – are more than just buzzwords. They are a reality if we want to stay relevant!

To stay updated with our series on Micro Services architecture follow us on twitter or subscribe to our blog.

Written By: Meghna Verma Meghna Verma is the Content Manager at Captain Dash.  You can reach her on Twitter @M3GV3RMa .