Martin Fowler - Microservices

The Microservice architectural style has become the hot fashion recently. This talk looks at some of the common characteristics of microservice architectures, what (if any) the difference is between microservices and SOA, how big a microservice should be, the trade-offs between a monolithic and microservice architecture, and some essential things you need to have in place when you first go live using this approach.
Software Development in the 21st Century (Part 3 of 3) - Originally delivered at ThoughtWorks XCONF 2014
www.thoughtworks.com/talks/sof...
Help us caption & translate this video!
amara.org/v/J2IG/

[@RonClabo]

I love that he points out that asynchronicity increases complexity. I think this fact is often overlooked in software architecture decisions.

[@richardhp77]

I built a project once where all the business logic was in modules, and each module communicated through a service which was injected at runtime. This meant I could deploy the entire codebase as a monolith, or just by changing the config files, deploy as independent services. This was done just by injecting a network based inter-module communication plugin rather than an in-memory option. Also the DB service was injected at runtime, so you could alter the config file and point each module at either the same DB or different ones, and also swap the DB drivers as well. Worked pretty well as I recall, and meant we weren't boxed into either architecture until later on down the line when we decided to deploy. Also meant the business logic could be tested independently of how the deployment was to be done.

[@dilneicunha]

Great.... What I see and understand after watching Martin Fowler is that many software development companies are migrating their applications to micro-services without skewing the whole context. Not with technical or sufficient discernment, then they do just by fashion. And when the decision is not technical enough, many of these projects go bad or even fail, today's developers are lazy, they do not improve, I see that if we do not have a team of seniors we must invest in the change of our culture before To move on.

[@AnujSharma-xo3qg]

thanks to Martin with a great explanation about micro services, especially when to use, where to use, how to use & not when to use.

[@mayanksj]

A very precise and concise introduction to microservices. Thanks Martin Fowler.

[@georgesmith3022]

Microservices are good in theory, but in practice there are many problems, i dont think there are many people who know how to do it right

[@vikassinghalld]

It always delightful to listen Martin Fowler

[@sagarjunnarkar8384]

Nice explanation!!!

[@southern_smacker]

Good explanation, Thumbs up!

[@KevinSheppard]

I feel like I could study under this guy.

[@zHqqrdz]

I'd be willing to work for free for him for 10 straight years just to know everything he knows.

[@JohnSanabria]

Where I can get the slides of this presentation?

[@Arjun-tg1go]

If someone reads about SOA principles as of today.. they would think Microservices are just another name for it... I think when SOA came out, companies implemented SOA using current technology at that time and it gave SOA a bad name...

[@suchoudh]

Superlike

[@chihabahmed5207]

Hi there, if i multiple services that they work independently ( will they still be called microservice)?

[@flaviuszoltan1754]

Multiple services that work independently is just one small characteristic, but is not enough to call it Microservices

[@_jfsanchez_]

If they do not interact at all, I think it's not microservices.

[@umeshdimri5599]

does microservice rise means that the end of soa is coming?

[@peterlee9915]

Umesh Dimri i don’t think so, micro service is just a realization of soa.

[@AlanCostaPlus]

He pointed microservices as being a subset of SOA. If anything SOA is being reinforced here.

[@xnoreq]

Microservices are a way of implementing SOA....

[@Arjun-tg1go]

No, as he mentioned Microservices are subset of SOA... so end of SOA means end of Microservices

[@sahild6584]

each service have different datastore, surely it will detoriate the app performance, because communication is happening over network, which is again a bottleneck.

[@flaviuszoltan1754]

I don`t see that a strong reason for using the same data store. The network communication issue can be solved, for example, by having services that communicate to each other deployed on the same data center.

[@evelynlima3769]

that's where docker containers comes to place, in the cloud

[@ksaweryglab]

So what would be the alternative? Some services can share the data store but I hear this argument over and over again that it's better if each service has its own.

[@JamesSmith-cm7sg]

Barely noticeable within the same network