InfoQ Homepage Microservices Content on InfoQ
-
Microservices and the Goal of Software Development
The goal of software is to sustainably minimize lead time to positive business impact, everything else is detail, Dan North claimed in a presentation at the QCon London conference describing ways of reasoning about code and how this leads him into an architecture style that may fit microservices.
-
Microservices and Evolutionary Architecture
Service-Oriented Architecture (SOA) made us think about breaking up monolithic systems into individual services but also encouraged building producer driven monster services with centralised control. With microservices we are going back to the underlying notions of why SOA made sense, Rebecca Parsons claimed in a presentation at the QCon London conference.
-
Characteristics of Microservices, Applications and Systems
The assumption that a large system must have a single environment, often with a one-to-one mapping between a project’s scope and the system built are challenged today Stefan Tilkov explains when looking into ways to split a large system into smaller parts and comparing the characteristics of systems, applications and microservices.
-
Google Releases gRPC, a HTTP/2 RPC Framework for Microservices
Google has opened sourced gRPC, a RPC framework used internally to connect cloud microservices. gRPC comes with support for 10 languages, making it attractive for creating back-end cloud services for mobile applications.
-
What is so Special about Microservices? An Interview with Mark Little
Mark Little discusses the anatomy of microservices, how they can be used, and why you may want to temper your enthusiasm to get them to production.
-
A Service View of Business Driven DevOps
Over the years Steve Jones has had a lot to say about Business SOA. Recently he's turned his attention to DevOps and believes there are some important lessons that DevOps can learn from SOA and Business Architecture.
-
Bad Practices Building Microservices
When adopting a microservices architecture, using an external architect to create the design of a service instead of helping a team make their own decisions about design and implementation is one of several traps or bad practices that Vladimir Khorikov has experienced in his work.
-
Don’t Share Code Between Microservices
Reasons for building microservices are often about using isolation as a means to handle change. Sharing code between services couples your services to each other reducing the effectiveness of the isolation and the ability to handle change, David Dawson writes in a series of blog posts questioning the Don’t Repeat Yourself (DRY) principle in connection with microservices.
-
Microservices, Containers and Docker
Working with a microservices architecture creating small services with a need for light-weight mechanisms, independent deployment, scalability and portability, a container technology like Docker can provide an ideal environment for deployment of these services with respect to speed, isolation management, and lifecycle.
-
State of the Art in Microservices
Moving to Continuous Delivery and speeding things up, the rate of change have increased at the same time as the cost, size and risk of change has reduced, an DevOps and agile transformation, and a containerization that is very compelling for businesses of nowadays, Adrian Cockcroft explained in his keynote at the recent Docker conference in Amsterdam.
-
Prana: A Sidecar Application for NetflixOSS-based Services
Netflix has released Prana, an open-source "sidecar" application the company developed to allow heterogeneous microservice applications to use the NetflixOSS JVM-based platform support libraries.
-
Monoliths from a Microservices Perspective
There is a strong trend for microservice based architectures and frequent discussions comparing them to monoliths, Robert Annett explains and defines a monolith as an architectural style or a pattern using three basic viewtypes for characterization.
-
The Future of Microservices
Microservices are not new ideas and we will over the course of 3-5 years end up rebuilding WS-* the same way Web Services did rebuild all from CORBA unless we learn from our mistakes and improve to prevent them from being made again, Greg Young stated in a presentation at the Microservices Conference in London.
-
Microservices as a Service-Oriented Delivery Model
Microservices are valuable, but to break things up properly creating the right boundaries we need to understand our business and its processes Jeppe Cramon stated in a presentation at the Microservices Conference in London.
-
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.