InfoQ Homepage Microservices Content on InfoQ
-
Netflix Play API: Building an Evolutionary Architecture
At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.
-
The Human Side of Microservices
A microservices architecture is a game changer for team communication, not a purely technical solution. If different teams don’t have stable, direct communication channels, the software they produce will suffer. The five key properties crucial for a successful microservices implementation are zero-configuration, auto-discovery, high redundancy, self-healing, and fault tolerance.
-
Building Production-Ready Applications: Michael Kehoe Shares Lessons Learned from LinkedIn
At QCon San Francisco, Michael Kehoe presented “Building Production-Ready Applications”. Drawing on his experience with site reliability engineering (SRE), he introduced the tenets of “production-readiness” that all engineers across the organisation should focus on as: stability and reliability; scalability and performance; fault tolerance and disaster recovery; monitoring; and documentation.
-
Axon Conference Panel: Why Should We Use Microservices?
In the panel discussion at the recent Event-Driven Microservices Conference in Amsterdam, Frans van Buul from AxonIQ, the conference organizer, started by noting that microservices are quite mainstream today. He wanted to look back at what we have learned, but also think about where we will be heading in the next couple of years.
-
Q&A with IBM's Lin Sun on Istio 1.0 and Microservices
InfoQ caught up with Lin Sun, a senior technical member at IBM and also a participant in the open source Istio project release team, regarding Istio in general and the 1.0 release in particular.
-
Strategies for Microservices Communication
When moving from a monolith to a microservices architecture, complexity implicitly hidden within the monolith becomes explicitly visible and the challenges for communication will grow exponentially, Michael Plöd explained in a presentation at GeeCON 2018, describing different strategies for communicating between microservices.
-
Experiences Using Micro Frontends at IKEA
Today, we commonly split up an enterprise architecture in smaller services, microservices. But we have the same problems with the frontend monolith as we had with the backend, Gustaf Nilsson Kotte explained in a recent interview hosted by Stefan Tilkov. Using a micro frontend architecture, he breaks the frontend into smaller parts, to allow for teams to deploy continuously and autonomously.
-
QLoo Creates GraphQL Interface for Existing Services
Solo.io recently released QLoo , an API translation layer to provide GraphQL endpoints for existing services and serverless functions. QLoo is intended to simplify the process of adding GraphQL on top of existing software.
-
Instana Releases Sample Microservice Application
Instana, provider of AI powered monitoring solutions for dynamic containerised microservice applications, announced at QCon New York the release of Stan’s Robot Shop, a sample microservice application that can be used as a sandbox to test and learn about microservice architecture, containerised application orchestration and automatic monitoring techniques.
-
Designing Microservice Architectures the Right Way: Michael Bryzek's Lessons Learned at QCon NY
At QCon New York 2018, Michael Bryzek discussed how to design microservice architectures “the right way”. Key takeaways included: engineers should design schema first for all APIs and events, as this allows the automated code generation of boilerplate code; and investment should be made in automation, such as deployment and dependency management.
-
Why Segment Returned to a Monolith from Microservices
Alexandra Noonan, from Segment, describes how they moved their original monolithic architecture to microservices and then found problems with that approach which required them to rethink and move back to a (different) monolithic architecture with far more appreciable benefits.
-
Entity Services Increase Complexity: Tareq Abedrabbo Discusses Microservices Antipatterns
Entity services are a microservices anti-pattern, writes Tareq Abedrabbo, independent software consultant. The core reason for this is that they form shallow modules, where the interface is complex in relation to the functionality it provides.
-
Complex Event Flows in Distributed Systems: Bernd Rücker Discusses Workflow Engines at QCon NY
At QCon New York, Bernd Rücker presented “Complex Event Flows in Distributed Systems”, and cautioned that although event-driven architectures can be extremely powerful, it can also be easy to create complex and highly-coupled peer-to-peer event chains. He proposed that lightweight, open source workflow engine solutions provide many advantages for the business, developers and ops.
-
QCon NY: Jonas Bonér on Designing Events-First Microservices
Events-first domain driven design (DDD) and event streaming are critical in developing a resilient and scalable microservices architecture. Jonas Bonér from LightBend engineering team spoke at QCon New York 2018 Conference last week about the events-first design.
-
Business Processes, Long-Running Services and Microservices
During recent years domain events are increasingly being discussed, but we should be discussing commands just as much, Martin Schimak explained at the recent DDD eXchange 2018 conference, where he covered events, command and long-running services in a microservices world, and how process managers and similar tooling can help in running core business logic.