InfoQ Homepage Microservices Content on InfoQ
-
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.
-
Microservices and SOA
Over the past year or so we've started to hear about Microservices as potentially new architectural style. Recently Thoughtworks' Martin Fowler and James Lewis wrote an article defining Microservices. However, Steve Jones takes issue with the general theme and much in that article, believing that there is little new here and this is just a Service Oriented Deliver approach.
-
GOTO Berlin: Microservices as an Alternative to Monoliths
James Lewis talked at the GOTO Berlin Conference about an alternative to the traditional way of building systems where all functionality is put into one big application with one big database, instead using a pattern where entirely separate business capabilities, together with their own data, are kept separate in microservices.
-
Netflix: Dystopia as a Service
A keynote presentation by Adrian Cockroft, Cloud Architect at Netflix, describes the Netflix "Cloud Native" architecture and the trade-off between the Utopia of perfection versus the new engineering challenge of building highly agile and highly available services from ephemeral and often broken components.