InfoQ Homepage SOA Content on InfoQ
-
The Difference between SOA and Microservices?
RedMonk's Stephen O'Grady has entered the debate on SOA versus microservices and agrees with many others that the size of a service is neither a necessary nor sufficient differentiation.
-
Aspects and Services - an Important Distinction?
Arnon Rotem-Gal-Oz believes that something is either a monolith or a microservice is nonsense. He also believes that more and more implementations which claim to be microservices will not live up to all of the principles. However, he does not discount the need for semi-independently deployable software components and discusses an approach he has found useful, which he call Aspects.
-
Q&A with Susan Fowler on Production-Ready Microservices
At the upcoming Microservices.com Practitioners Summit on Jan 31, Susan Fowler, an engineer at Stripe, will be presenting on topics from her book, Production Ready Microservices. InfoQ met with Fowler to discuss the technical, business and cultural challenges of successfully implementing a microservices architecture.
-
Q&A with Matt Klein on Creating Envoy at Lyft
At the upcoming Microservices.com Practitioners Summit on Jan 31, Matt Klein, a senior software engineer at Lyft, will be presenting his work on Envoy, a Layer 7 communications bus used throughout Lyft’s service-oriented architecture. InfoQ met with Klein to discuss the benefits of creating a custom tool for Lyft’s networking needs, and how it could benefit other microservices architectures.
-
Sharing Experiences from a Microservices Journey
In our continued effort to showcase lessons learned by microservices practitioners, we look at an article Piotr Gankiewicz has recently written with his own tips and tricks. These include references to CQRS, asynchronous architectures, service discovery and how choosing the right database for each service is important.
-
The Long History of Microservices
Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.
-
Komand Principal Engineer Sean Kelly on Microservice Fallacies
Sean Kelly, a Principal Engineer at Komad, has written about his experiences around microservices and five "truths" which developers believe microservices will bring to their architectures, applications and teams, but which, in his view, are not always the case.
-
Service-Based Architecture as an Alternative to Microservice Architecture
ThoughtWorks director Neal Ford argued in a recent talk that organizations transition more easily from a monolithic architecture to a service-based architecture than to a microservices architecture. Ford spoke at UberConf 2016 about service-based architecture, a middle ground between service-oriented architecture and microservices.
-
Microservices Imply a Distributed System
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
-
Breaking a Monolithic API into Microservices at Uber
In a recent blog post, Uber engineer Emily Reinhold described how they broke a monolithic API into a modular, flexible microservice architecture. She highlighted a few key design and architectural choices that were key to Uber’s migration effort.
-
Juval Löwy: Why Every Class Should Be a Service
Juval Löwy has pioneered a method of building service-oriented applications in which each class represents a service onto itself. While these applications may initially seem like 'class explosion', they are actually the product of a truly decomposed system; one that has been properly analyzed and designed. Juwal explains his intent and describes how development teams can improve from this process.
-
Lessons Learned at the O’Reilly Software Architecture Conference: Day One
This article presents a review of the first day at the O'Reilly Software Architecture conference, held in New York City 12-13th April. Sessions summarised include, ‘blah, blah... microservices...blah, blah’, ‘the evolution of evolutionary architecture’, ‘Death Star Security’, ‘Twelve Patterns for Hypermedia Architecture’, ‘Architecture Without an End State’ and 'Leading Simplicity'.
-
Microservices Ending up as a Distributed Monolith
Services requiring an enterprise platform built of 100s of shared libraries to be able to run and only allowing approved network clients for talking to services are two anti-patterns, Ben Christensen explained at the recent Microservices Practitioner Summit sharing his experiences from building distributed systems and the trend he sees in increased coupling with binary dependencies.
-
SOA versus Microservices?
Microservices and SOA are often compared and contrasted, with some people suggesting they are unrelated whereas others believe they are close relatives. In a recent article Matt Braiser joins the debate on the side of the latter group and gives his reasons for believing that microservices owe their existence to the success of SOA principles.
-
Microservices and Integration from an Enterprise Perspective
Common misconceptions in large enterprises that Kim Clark meets are that microservices are fine grained WSDL operations or that APIs are microservices. A reason for this is that they are confusing interface granularity with component granularity, Clark claimed in a presentation at this year’s Microservices Conference in London.