InfoQ Homepage SOA Content on InfoQ
-
A Critical Look at Microservices for the Enterprise
Udi Dahan describes how looking for highly cohesive, loosely coupled microservices, not within a system but over the enterprise, we can end up with a focus on organising services around business capabilities spanning the whole organisation since this is what the business care about.
-
Rebuilding Wunderlist Using Microservices
Chad Fowler, CTO at 6Wunderkinder, the company behind Wunderlist, describes how they went from a large monolithic Rails application and a large monolithic database to a system with many microservices, and the architecture they ended up with. Starting by adding new functionality as services and splitting the large database into smaller databases, they ended up doing a big rewrite of a new system.
-
Martin Fowler on Characteristics of Microservices
Service-Oriented Architecture (SOA) is a very broad term and practically meaningless. Microservices is a subset of SOA with the value being that it allows us to put a label on this useful subset of SOA terminology, Martin Fowler stated in his keynote introducing Microservices when opening the GOTO Berlin Conference 2014.
-
Apache Camel 2.14: Java 8, Spring 4, REST DSL and Metrics
The Apache Camel team recently released version 2.14, their 66th release. Camel is an open-source integration framework that provides components based on the popular enterprise integration patterns. It allows an application to define route and mediation rules in many domain-specific languages (DSLs), for example with Java, XML, Groovy and Scala.
-
Lessons Learnt Using Microservices
Several companies have reported their move to adopting Microservices. Recently Tom Livesey from startup Droplet has joined the discussions by posting several lessons they learnt when moving to that architectural approach.
-
Microservices vs Monolithic Applications
Using microservices is one way of breaking up a monolithic application to gain increased decoupling, separation of concerns and fast deployment but it’s not the only or even the best way, Todd Hoff states comparing the two architectural approaches.
-
Microservices and the Big Ball of Mud
Recently several articles have been written which wonder whether microservices offers a better way of architecting systems or represents a potential problem waiting to happen: distributed Big Balls of Mud. Simon Brown and Gene Hughson discuss the possibility that until people can write well architected monolithic systems they're unlikely to benefit from microservices.
-
The Future of Docker
Jeff Lindsay, creator of Dokku and early Docker contributor, discussed in an interview by CenturyLink the Docker related projects he is working on, and how they aim to solve the problems involved in a next generation Docker-based service oriented architecture.
-
Udi Dahan on Service-Oriented Composition
Udi Dahan describes how we in a Service-Oriented Architecture (SOA) where client-side components for one service runs in the same process as components for other services can collect several logical calls into one larger physical call to avoid the high cost, in terms of client to server communication, that otherwise could be substantial.
-
Karma Refactors to Microservices
It's one thing to build a microservices application from scratch, quite another to refactor the architecture of a running application. Karma is doing exactly that and finding benefits and challenges of microservices architecture as they go.
-
Lessons Learned Building Distributed Systems at Bitly
At the Bacon Conference last May, bitly Lead Application Developer Sean O'Connor explained the most relevant lessons bitly developers learned while building a distributed system that handles 6 billions clicks per month.
-
Patterns for Building and Deploying Microservices
Managing micro-services means looking after lots of small systems talking to each other and automated provisioning as well as infrastructure automation is crucial, James Lewis states when sharing techniques and practices that have helped him manage the increased operational complexity a microservice architecture gives.
-
The Term µServices Already Defined Four Years Ago
“I coined the term µServices four years ago defining them as services that always communicate within the same process, without any overhead, as a way to separate these lightweight services from the heavy, costly, and complex services people tended to think about because of the advent of Service Oriented Architectures (SOA)” Peter Kriens recently claimed.
-
An Introduction to Microservices Design
Designing for simple components and systems is key when moving to microservices. The focus is on evolution of components and how we build systems that allow evolution and change, Russ Miles recently stated in an introduction to designing and building microservices.
-
Designing SOA Systems with ServiceMatrix
The Particular Service Platform has four headline components: ServiceMatrix, ServiceInsight, ServicePulse, and the well-respected NServiceBus. Over the next few weeks, we’ll be looking at each in turn starting with ServiceMatrix, their SOA design tool.