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. Micro Services

As we have often discussed on the Captain Dash blog, Micro Services refer to a set of services or mini applications making up the application architecture of an organization.

An organization can either break apart an existing Monolithic application to create Micro Services or it can create its architecture as a combination of several Micro Services from scratch.

Micro Segmentation

Micro Segmentation on the other hand deals with breaking up of a network itself. This could be done for several reasons, foremost of which is security.

The point to note though is that when a team uses the Micro Services approach to their architecture a natural bifurcation of the network occurs thus leading to Micro Segmentation. This is also the reason why there can be confusion between the two.

Another significant use for Micro Segmentation is that aside from taking the pressure off of one large network is that it isolates disruption when services need to be changed or upgraded. In case of a single large network one change can have domino effect on the whole network.

Micro Services and Micro Segmentation

In brief these are both methods of segmenting a Monolithic architecture in different domains and turning them into smaller, more scalable and secure components.

Just because a team uses one approach it doesn’t automatically mean that the other follows. Though it is best practice to employ both for optimization.

While one cannot say which one comes first, as a general rule it has been observed that if a team uses Micro Services then Micro Segmentation is quick to follow. On the other hand the employment of Micro Segmentation does not necessarily result in the use of Micro Services by a team.

If your organization has made the switch to Micro Services or to Micro Segmentation we would love to hear which came first for you.

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

Written By: Meghna Verma

Three architectural strategies for Micro Services APIs

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.

Read More

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 - 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.

On the other hand it has its fair share of challenges, the most prominent one being that separate libraries need to be maintained for each language used. While such an overhead seems acceptable for 2-3 languages, what happens when we are dealing with 6-8 of them?

Organizations traditionally used virtualization to tackle this issue but with the arrival of Docker on the scene most have moved to containers because of lower overheads. But, containers in Micro Services do exactly what they do in a home – they hide the mess not get rid of it! In this case the libraries still need to be built to facilitate communication except they are containerized.

Here is where sidecars come in. Named after the sidecars on a motorcycle a sidecar is a second application that runs alongside the Micro Service it is attached to and provides a language neutral interface for the micro service to communicate with. It can be said that a sidecar is a glue code that allows for the assembly of various Micro Services components.

Many teams are currently employing sidecars successfully for example Netflix and AirBnB.

They do, of course, come with certain disadvantages. The most obvious being that in process communication is smoother and less prone to bugging. Another issue being that sidecars cannot effectively access all the information inside the parent application.

There is also the point to consider that eventually sidecars will become obsolete because the Micro Services systems are evolving even as speak. Until that happens though the sidecar pattern is a great tool to add to your Micro Services set to facilitate communication and language neutrality.

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 CMO at Captain Dash.  You can reach her on Twitter @M3GV3RMa .

 

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 - 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.

So, now we are faced with the question of why should one partition the system? The simple answer, of course, is agility. The biggest reason for any organization to switch to Micro services is to be agile.

And agile is all about individuals; how they decide to work together and build software that are aligned with their business goals.

There are a few broad reasons why businesses partition either their organizational or their software structure:

Comparative Rates of Change

Different parts of a system often have different rates of change relative to each other. Some portions might need to be changed on a weekly basis while others annually. In a case such as this a partitioning is usually required so as to make the more frequently changed parts to be more independent.

Autonomy of Teams

Sometimes it is easier to split up teams and systems so that different teams can work independently on different parts of the system without being affected by each other’s work and speed. Here the teams are usually created so as to mimic the independently partitioned system parts.

Domain Boundaries

A complicated system often calls for extremely strict and independent boundaries of its business domains. This is to make it possible for each business unit to be completely self-sufficient and thus be independent of the functioning of any other unit. This is usually what we called decoupled business units. Having separate teams and modules taking care of these domains is usually a good idea.

Non-Functional Facets

Usually different parts of a system will have differing non-functional facets, which put them at odds where, needs and resources are concerned. This is the reason that Monoliths are difficult to scale since the entire system needs to be scaled even if only one single component needs it. This is another reason businesses consider partitioning their systems since doing so helps them to better assign their resources and invest their energies.

The bottom line? No matter what the reason for the partitioning maybe the goal is agility!

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 CMO at Captain Dash.  You can reach her on Twitter @M3GV3RMa .

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

 

A great talk on the practical aspects of the Micro Services architecture. Sam Newton talks about things you need to learn along with the challenges you can face and how to go about navigating your team through the implementation of such architecture. He talks about his own experiences and what he learnt from his own failures.

2. Services and Rails: The Shit They Don’t Tell You

By Brian Morton , software engineer @ Yammer

Screen Shot 2015-07-07 at 16.08.49

Brian Morton from Yammer talks about how to build services and integrate them into rails. This talk looks into mistakes made, solutions that worked for Yammer, monitoring cost versus viability, teams and how Yammer has ben able to move quickly. Overall a comprehensive talk that is easy to follow even for non-engineers.

3. Microservices

By Martin Fowler, programmer @ ThoughtWorks

Screen Shot 2015-07-07 at 16.01.44

A video by Martin Fowler has to be included in this list. This video discusses what are Micro Services, what they do, how they differ from monoliths and whether they are such a new concept after all or not. This is a basic, introductory talk on the subject by one of the people who has explored it in great depth. His blog is a great read too for someone interested in further information.

4. The Business Benefits of Micro Services

By Russ Miles, chief scientist @ Simplicity Itself

Screen Shot 2015-07-07 at 16.02.24

A short, to the point video on how Micro Services can benefit a business beyond the dev team. This talk is for everyone whose company has invested in or is thinking of investing in a Micro Services architecture. It helps people who are the most removed from technology in an organization understand exactly how Micro Services can help a business compete and stay alive.

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 CMO at Captain Dash.  You can reach her on Twitter @M3GV3RMa .

Monolith to Micro Services - Refactoring a Monolith

So how does one refactor a Monolith? It is not often that we are awarded the opportunity to start with a blank page where service architecture is concerned. In fact some of the most successful Micro Service based architectures that we see today started out as Monoliths!

Read More

Micro Services - Google Translate That Works!

To put a layman’s twist into this let’s say that micro services are a Google translate that actually works!

Read More

Quels oeufs de Paques se cachent dans votre architecture ?

Pendant la période de Pâques, observez bien les œufs en chocolat.

Pâques vient de passer. Rappelez vous des oeufs en chocolats dans votre jardin.

Pourquoi diable les œufs, vous demandez-vous ?

Simplement parce que c'est une belle allégorie de ce que pourrait être votre architecture informatique.

Commençons par le traditionnel œuf de Pâques auquel tout le monde pense, le gros oeuf en chocolat. Cet œuf, c'est votre architecture Monolithique standard.

chocolate-easter-egg_1427389013

C'est une grande quantité de chocolat, très appétissante au début, mais qui se révèle finalement indigeste, vous fait grossir et vous ralentit, car il faut la manger en une seule fois sinon elle se gâte.

Les Micro Services en revanche, sont comme de minuscules oeufs de Pâques. Ces oeufs sont constitués de la même quantité de chocolat que le gros œuf , mais sont beaucoup plus petits et nombreux. De cette façon, vous pouvez les manger au rythme qui vous plaît. Selon votre appétit, sans vous rendre malade ni grossir. Et la quantité de chocolat que vous consommez suffit à vous apporter un regain d'énergie.

mini-eggs-002

A l'image des petits oeufs éparpillés dans votre jardin, les Micro Services fonctionnent de manière indépendante et peuvent être utilisés comme on veut. Ces programmes poids-plume procurent à votre activité la souplesse et l'extensibilité nécessaires pour rester compétitive et pertinente.

La prochaine fois, n'oubliez pas de prêter un peu d'attention à cet œuf en chocolat que vous êtes sur le point de consommer !

Note : Captain Dash commence une nouvelle série d’articles sur les Micro Services. 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 - Built For Failure

At Captain Dash we love to fail!

Why, you ask? Because, failure, is the best way to succeed. And our choice of architecture reflects that.

Failure

In any service there are bound to be glitches and a service can fail at any given time, be it Monolithic or Micro Services based. As the service provider it is our job to detect those failures quickly and to repair them.

In a typical Monolithic structure, due to the complex layers, it is often difficult to detect the source of failure easily and then to keep in mind all the internal dependencies to make sure that something else is not affected in the repair process. Finally the actual testing and deployment takes a long time.

Micro Services on the other hand are built for this kind of failure. The idea behind the multiple decoupled services is that when one goes down the others are not affected. Further, given the emphasis on coordination and event collaboration there is a tendency to monitor the structure constantly. This results in purposefully crashing the applications just to see what they can withstand and how they can be bettered. An example of this is the Netflix’s Simian Army that we talked about in our post about anti-fragility.

Given the size of the code involved along with the speed of deployment the ability to fix and change each application individually provides us the flexibility to innovate regularly and test as often as we please. This flexibility to innovate is what gives us the confidence to fail and thus create at a rate fast enough to be agile and cause disruption.

Ultimately it is the confidence to fail that gives a team the confidence to push the limits of the accepted industry norms, to seek out what is deemed impossible. This freedom to create that Micro Services allow us is what makes us love failure.

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 .

 

 

 

 

 

 

 

 

Qu’est ce qu’une Application Monolithique ???

Un Monolithe est un bloc de pierre de grande dimension, constitué d'un seul élément, naturel ou taillé voire déplacé par l'Homme.

Et nous français, avons grandi avec ce symbole du monolithe ultime : le menhir d’Obelix.

Nous avons pris pour habitude de qualifier de monolithe les grosses applications, constituées d’un seul bloc, dont l’ambition est de traiter toutes les demandes que nous leur soumettons.

allocation

Ces applications sont écrites dans un langage unique. Et à chaque ajout elles deviennent de plus en plus complexes, difficiles à maintenir et déployer.

Pour faire face à cette complexité, les architectures sont souvent scindées, au plan logique et non physique, par fonction. Plus les systèmes grossissent moins ils deviennent réactifs.

Seul un Obelix, tombé dans un chaudron de potion magique à sa naissance, est capable de manipuler avec dextérité ces Menhirs de technologie.

Les Monolithes obligent les entreprises à répartir leurs ressources par projet. Ainsi on empile autant de consultants et de développeurs qu’il existe de projets. Une multitude de strates s’interposent entre le développeur et l’utilisateur final.

Le Monolithe devient une fin en soi. C’est autour de lui que s’organisent les équipes, que se concentre l’énergie.

Et c’est là que les Micro Services deviennent révolutionnaires. Ils permettent d’organiser autour des Monolithes une série de petits services autonomes, connectés entre eux par des APIs.

Grâce aux Micro Services, le monolithe qui était auparavant un Mehnir issu de l’ère Néolithique se transforme littéralement en une source de vie. Un puits inépuisable où les Micro Services pourront puiser de la data et donner vie à une multitude de nouveaux services.

Note : Captain Dash commence une nouvelle série d’articles sur les Micro Services. 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 Vs Monolithic Architectures

In the last 3 weeks we have outlined in different posts the salient points of what is a Micro Services architecture and a Monolithic Architecture. This week we bring to you the main differences between the two.

[table id=1 /]

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 .

What kind of Easter Egg Hides in Your Architecture?

This long weekend as you celebrate Easter pay close attention to the eggs. Why eggs you ask? Because Easter eggs can help you determine where your business stands in terms of architecture and what are its long-term effects on your business.

chocolate-easter-egg_1427389013

Let’s start with the proverbial, large chocolate egg that one thinks of when we say Easter. This Easter egg is your standard Monolithic architecture. There is a lot of chocolate that feels good to begin with but eventually makes you sick, fat and slow. You finish it in one go or else it goes bad. A Monolithic architecture too is limited due to its huge size and all the weight it carries makes your business slow.

mini-eggs-002

Micro services architecture on the other hand, is like little mini eggs. These eggs are made of the same amount of chocolate too but are small and numerous. Thus, allowing you the flexibility of eating them as and when you need over as much time as you prefer. This means that you don’t get sick, don’t get fat and they provide just enough chocolate to give you an energy boost! Microservices with their small scalable format, too, allow you the flexibility of creating your architecture, as you want, in any language you want. Just like the mini eggs, Microservices are loosely coupled. They function as separate entities, which gives us the ability to use them in any manner we want. These lightweight codes provide the agility and scalability your business needs to stay competitive and relevant because agility will not be a competitive advantage in coming days – it will be a necessity.

At Captain Dash we have come to rely on this very flexibility of Microservices to build user centric dashboards that are quick to update, change around as required and work across all devices.

So, again, as you go about your festivities give some consideration to that egg you are about to consume!

Note: Subscribe to our blog or follow us on twitter to know read more about Micro services architecture. We put up a new post every week.

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