Microservices vs. SOA
Stefan emphasizes the critical role of the user interface in microservices, arguing that it should be an integral part of the service rather than an afterthought. He contrasts this with traditional SOA, highlighting that microservices should operate as self-consistent systems with their own logic and persistence, ideally developed by a single team. The discussion reveals a shift towards smaller, technology-independent services that enhance overall system coherence.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 210: Stefan Tilkov on Architecture and Micro Services
Related Questions
What I don't like as an approach is having a front end application, a front end application that actually invokes lots of services. Because I think we're then making a strong mistake. What are your thoughts on why this approach might be flawed?
To me, SOA was always about sort of an enterprise strategy to really take all of your IT, separate it in different services, and then somehow get a benefit from that. It seems to me the difference to this new approach is that in fact we are just talking about one system that provides one kind of service to some customer that is composed of different services. What do you think about that? Is that a distinction between SOA, or am I getting something wrong here?