Video není dostupné.
Omlouváme se.
Microservices vs. service oriented architectures
Vložit
- čas přidán 5. 08. 2024
- Microservices break down applications into small, flexible pieces that can be run and managed independently. Learn how microservices are different from service oriented architectures (SOAs) and how they allow faster, easier application deployment. Also, learn how Red Hat can help you get started with microservices and migrate a monolithic architecture.
Learn more: redhat.com/en/developers
Here are a couple of specifics that I appreciated, and that I had not heard in other presentations of Microservices vs SOA:
--With SOA, the service was deployed on the Enterprise Service Bus, and you couldn't just improve the scale (performance) of one service--instead you had to scale the entire ESB. Microservices can be scaled independently.
--With SOA, if the ESB needs to be patched, you potentially affect every service on the ESB.
short and sweet! wonderful! thanks
One does not need an ESB to do SOA. ESB is an architectural pattern just like a microservice architecture (MSA) is a pattern. Martin Fowler (I think was the first) even called microservices a subset of soa. There is nothing wrong with either approaches- they are applicable patterns for various problems. There are a number of platforms / tools, that can support many architecture and deployment topologies. I would be hesitant to build a new system using a MSA without involving a platform to solve the first 75% of the software stack. Then I could focus my effort on the last 25% which should be the part that pays for it all. Once the money flows in one can start to reinvent the wheel to save on cost- though even then it might be easier / cheaper to give some gold coins for a proven baseline.
Thanks a lot, Very informative.
Quality and clear.
Is there a significant latency difference between soa and micro service due to messaging?
Thanks, Very good!
Thank you!
Wow, amazing information
Thank you.
Concepts wise its Good explanation guys, but on implementation specifics and on real value add not finding much. One point I got this video like for SOA based u need ESB, where as MicroService self container based-Docker which is free. Other one like not required heavy configuration, XML binding etc with Microservice which is there with SOA. But if your SOA based application which is not using ESB, then what will be the value add point to move/migrate to Microservice ?
Satyajit Sethy the most significant benefit I see is that microservices makes the components so small, self contained and easily deployable, that it's a netter fit for agile development and is more in line with DevOps practices these days. Monolithic web services are difficult to scale and evolve because of their size, which I think microservices will help drastically about.
@@CharleyDC5R That's regressive and doesn't answer the question at all !
It's good to hear that if people have to upgrade with technology modernization, SOA technologies like transaction-management, messaging, O-R mapping, business rule management will also have to be find there places in MicroServices world.
What does ESP mean?
It sounds like ESP to us :) But it is ESB, the Enterprise Service Bus.
It is a sexual transmitted disease
I was watching how to make front page on internet and now I am here
you need to have a nap, believe me, less coffee and more sleep
we might have the same thinking, you know what i mean
Kent's comment about individual services cannot be scaled in an ESB is not true, you can scale individual services in an ESB.
Right, Many tools like WIly can help to individual scale the services.
I don't even know what this stuff is, but after watching this, I know what this stuff is, but I still don't really know what it is, but I kind of know what it is
Its how we fake that our(it) job so much complexes to make more money
Thank you!