InfoQ Homepage Microservices Content on InfoQ
-
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.
-
Application Architecture is Shifting towards Connected Apps
Anne Thomas has summarized in a webinar the shift from large applications to small focused apps relying on services, while Matias Duarte has spoken in an interview about connecting these apps.
-
Developing Microservices for the Cloud
When working with Microservices pushing them to the cloud, people often find it difficult to understand the new architecture, it’s a paradigm shift, Daniel Bryant explains in a presentation at the Microservices Conference in London. As a help when designing and implementing cloud microservices Daniel has created the DHARMA principles, the idea being to use them as a checklist.
-
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.
-
Martin Thompson Discusses the Reactive Manifesto 2.0
The second version of the Reactive Manifesto was announced at September's GOTO conference in Aarhus. Martin Thompson discusses the need for a revised version of the Manifesto and what its changes mean for the burgeoning reactive community.