Sushi, Bento and Microservices

japanese food to help to see software

Sushi Restaurant

What Is Bento?

Bento is a single-portion takeout or home-packed meal. Traditional bento holds rice, fish or meat, with pickled or cooked vegetables, usually in a box-shaped container. Containers range from disposable mass produced to hand crafted lacquerware. Japanese homemakers often spend time and energy on a carefully prepared lunch box for their spouse, child, or themselves. [WIKIPEDIA]

Bento is Not Sushi Restaurant!

In modern Restaurant some ribbon make it possible to consume patterns of little portions of sushi; in the middle, a powerful set of sushi-master repeatedly produce enough sushi to make it possible for everyone to eat. Ehi!...but this is the Monolith!

Bento Art

In little box you can be focused on details and create Art since everything is clear and you can easy take control.

Size is Important: smart things can be done if you master your creation and you can stay focused!

...but Restaurant!

In sushi restaurant everyone can eat, maybe sometime you need to wait to obtain the right dish you wish but, however, you will be fed! If you want feed more people you increase the number of sushi-master...

In the Monolith, if everything can work, everyone will take the result of service invocation; if you increase resources, you can offer more...but we already know: there are some limits!

Bento is Good!

Using the Bento everyone has a little box with everything needed to eat: no wait, no delay, all is easily available!

The box can be easily moved, you can eat a little and resume later. You can decide how to eat because everything is already there: the user need only to open the box, look what inside and consume!

A Microservice is specialized software, in the past we would call it Component, but a Microservice is more focused than a Component

You can move it for more and different deploy. You can easily use it: there's a simple and effective interface

A Microservice can be complex, but normally, whom has built it, is able to master it

Bento and details

Bento is homemade by mom or by yourself with patience and love

Microservices are built by little a team aware of what they want to achieve and they do their best. They master every aspect of Microservice they built!

Bento is not good to share!

What if, people on the same table, want to share elements of their Bento?

● maybe who is faster, he will eat better

● maybe everyone is polite but the organization create delay, difficult decisions or some food is wasted

● maybe favourite things aren't enough and everyone is unhappy

● maybe someone propose to go to restaurant

Bento & Microservices (1/2)

To make collaborative Microservices can be a serious problem

● which protocol to use?

● how to avoid chaotic or chatty communication?

● how to preserve reuse and clear bounds of services?

Bento & Microservices (2/2)

Governance of Microservices can be difficult:

● you need some more smart thing than a Registry

● you need to monitor fast evolutions

● if every microservice team is indipendent, you need to govern teams very well

● you need rules wise enough to be adopted but without constraint on the teams

● you must be able to afford trashing services and be fast enough to build new ones

…So...At the End?? (1/2)

Bento Art is amazing...but better if you can decide between use a Bento that day or go to Restaurant! Freedom to choose it's important and so, it's important to be aware of the consequences. You're ready?

Also it's important to have good friend with which eat and however someone that able to be a great cook, maybe tomorrow he will prepare amazing Bento for you!

…So...At the End?? (2/2)

If you need to feed some Business Partners, you'll decide to go to restaurant...but you're always sure of the restaurant that you choose?!?!?

...better to be able also to make an amazing Bento to surprise everyone!

Resources

http://www.pinterest.com/TheBigAWord/bento-box-art/

http://blog.arkency.com/2014/07/microservices-72-resources/

http://rclayton.silvrback.com/failing-at-microservices