InfoQ Homepage Microservices Content on InfoQ
-
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 Shared Libraries
Robert C. Martin's advice is to start with shared libraries and a plugin architecture and only when that becomes insufficient consider microservices. Giorgio Sironi argues against this, emphasising how different interactions between microservices are compared to interactions between objects and warns for the cost of retrofitting microservices over an existing code base.
-
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.
-
Experiences from Failing with Microservices
Different views within the team on the benefits and drawbacks comparing a microservice architecture with a more traditional monolithic architecture was one of the major reasons we failed, Richard Clayton writes sharing his experiences and reasons for failing when implementing and maintaining a microservice architecture.
-
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.
-
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.
-
OSGi Release 6 Specifications add Data Transfer Objects and Versioning Annotations
At last month's OSGi DevCon in New York, the OSGi Alliance released OSGi Core Release 6. This adds a standard for representing Data Transfer Objects and a way of annotating interfaces indicating whether they are supposed to be implemented or used by clients. In addition, an osgi.native namespace and extension bundle activators have been added; read on to find out more.
-
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.
-
Top Docker Misconceptions
Based on his experience as a system administrator evaluating Docker, Matt Jaynes has written at the DevOps University website about the top Docker misconceptions, warning about adopting Docker at small scale and without solid infrastructure foundations, and providing alternatives to improve the deployment process.
-
Moving from a Monolith to Microservices at SoundCloud
Moving SoundCloud into a microservices architecture has been essential in enabling our teams to develop production-ready features with much shorter feedback cycles, Phil Calçado writes in a three-part series sharing their experiences moving away from a monolithic system.
-
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.
-
The Strengths and Weaknesses of Microservices
There has been significant buzz around microservices lately, enough to generate some hype. After implementing heavy and cumbersome SOA solutions for more than a decade, are microservices the solution the industry has been waiting for? Or, are microservices simpler than monolithic solutions?
-
Microservices? What about Nanoservices?
Arnon Rotem-Gal-Oz has written an article following on from other discussions around the term Microservices and whether and how it relates to SOA. According to Arnon, this could be a slippery slope towards the Nonoservices anti-pattern, especially as some people define a Microservice in terms of lines of code.