InfoQ Homepage Distributed Systems Content on InfoQ
-
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.
-
Distributed, Fault Tolerant Transactions in NoSQL
Five years ago many NoSQL databases were pre version 1.0 and when, it came to the CAP tradeoff, choosing availability over consistency was in vogue. Fast forward to today and distributed, fault tolerant transactions are moving into the fore as a new round of NoSQL databases seek to redefine our NoSQL expectations.
-
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.
-
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.
-
Sharing Data Between Bounded Contexts in Domain-Driven Design
When using Domain-Driven Design (DDD) separating the concerns of a large system into bounded contexts with each context using its own data store there is often a need to share some common data. One way of doing that is to let each context publish events about changes, events that others can listen to, Julie Lerman recently explained in MSDN Magazine.
-
“Age of Ascent” Case Study Highlights Cloud as Game Delivery Engine
Microsoft recently published a case study describing how a massively multiplayer online (MMO) game used Microsoft Azure to support tens of thousands of players in a single space battle. The case study looks at how architectural considerations like connectivity, latency, and scale can be addressed in an elastic cloud environment that must respond quickly to unexpected bursts in demand.
-
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.
-
Building Distributed Systems - Technology Considerations
The success of the RICON conference is a testimony to the importance of big applications in industry today. InfoQ speaks to RICON host Basho Technologies about considerations in building distributed systems and technical lessons learned at the conference.
-
Basho Technologies Hosts RICON Distributed Systems Conference
Basho Riak is emerging as -the- highly scalable NoSQL database. InfoQ talks with Basho CEO and President Adam Wray, and Peter Coppola - VP of Product, about the RICON conference, and about Basho, Riak, and distributed systems.
-
Leslie Lamport on Distributed Systems and Precise Thinking
Leslie Lamport is the author of some of the most cited computer science papers and won a Turing Award in 2013 for his seminal work in distributed and concurrent systems. This is a summary of an interview that Lamport gave to Software Engineering Radio touching themes such as his early work in distributed systems and the importance of precise thinking in programming.
-
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.