InfoQ Homepage SOA Content on InfoQ
-
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.
-
Microservices Conference in Stockholm and London due Early November
The second Microservices Conference arranged by Skills Matter is due early November with two days in Stockholm and London respectively. The list of speakers include the program lead for the conference Russ Miles, David A. Dawson, Björn Carlson, chief architect at Klarna, Viktor Klang, chief software architect at Typesafe, Ian Cooper and Daniel Bryant.
-
Lessons Learned Working with Distributed Systems
Preparing for problems like partial failure is the best thing you can do when working with distributed systems, Vaughn Vernon explains in a conversation with InfoQ and refers to a blog post by Jeff Hodges noting its down-to-earth approach and practical advices e.g. designing for partial availability, and using capped exponential back off to restore full operation when dependencies are unavailable.
-
Design of a Hypermedia REST API Server and Consuming Client
REST and hypermedia has a lot of benefits but they significantly complicates building both the client and the server API, thus useful only in some scenarios Jimmy Bogard states in a series of blog posts highlighting what’s needed to get a full hypermedia solution from server to client including choosing a hypermedia-rich media type.
-
Udi Dahan on Reuse in Business Logic and Microservices
Reuse has been a watch word for almost everything that has happened in system development during the last thirty years, but reuse is like cyanide; in really small portions it can be healthy, using it too much it starts doing a lot of damage, Udi Dahan claimed in his presentation giving a different perspective on business logic at this year’s DDD Exchange conference in London.
-
Scaling the Stack Overflow Monolithic App by Obsessing Over Performance
At QCon New York 2015, David Fullerton presented a deep-dive into the monolithic C# / MS SQL architecture that powers the Stack Overflow website, which handles over 4 billion requests per month. Fullerton argued that by focusing on performance, scalability was included ‘almost for free’; and that by minimising the number of external application services, the need to pay ‘SOA tax’ has been avoided.
-
Stefan Tilkov: Skip the Monolith, Start with Microservices
During the last months Martin Fowler among others have claimed that a microservices architecture should always start with a monolith, but Stefan Tilkov is convinced this is wrong, building a well-structured monolith with cleanly separated modules that later may be pulled apart into microservices is extremely hard, if not impossible in most cases.
-
The CRM Landscape as Viewed by Teamleader
Last month, Teamleader won the HenQ award of the Boost competition at The Next Web Europe 2015 in Amsterdam, Netherlands. Benny Waelput from Teamleader discusses about the present and future of CRM systems.