Martin Fowler - Microservices

Рет қаралды 213,669

Күн бұрын

Пікірлер: 29

@RonClabo 9 жыл бұрын

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

@richardhp77 4 жыл бұрын

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 7 жыл бұрын

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.

@mayanksj 9 жыл бұрын

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

@AnujSharma-xo3qg 8 жыл бұрын

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

@vikassinghalld 7 жыл бұрын

It always delightful to listen Martin Fowler

@georgesmith3022 5 жыл бұрын

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

@KevinSheppard 8 жыл бұрын

I feel like I could study under this guy.

@zHqqrdz 7 жыл бұрын

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

@southern_smacker 7 жыл бұрын

Good explanation, Thumbs up!

@JohnSanabria 9 жыл бұрын

Where I can get the slides of this presentation?

@sagarjunnarkar8384 8 жыл бұрын

Nice explanation!!!

@Arjun-tg1go 4 жыл бұрын

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 5 жыл бұрын

Superlike

@sahild6584 8 жыл бұрын

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

@flaviuszoltan1754 6 жыл бұрын

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 5 жыл бұрын

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

@ksaweryglab 5 жыл бұрын

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 4 жыл бұрын

Barely noticeable within the same network