InfoQ Homepage Microservices Content on InfoQ
-
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.
-
Strategies for Decomposing a System into Microservices
A couple of years ago, Vladik Khononov and his team decided to start using microservices, but a few months later they found themselves in a huge mess. They concentrated on new cool technologies instead of thinking about how to decompose a system into microservices — finding the boundaries and where different functionalities should be located among these boundaries.
-
Observability and Microservices: The Need for Effective Tracing and Metrics
Zach Jory has written an article discussing how microservices and service mesh implementations need observability to ensure that developers can build cloud-native applications which scale and can be more easily managed. This ties into a number of articles and interviews we have spoken about over recent months too.
-
Instana Extends AI Application Monitoring to AWS Lambda
Instana, a cloud-native provider of artificial intelligence based monitoring tools for dynamic containerized microservice applications, has extended support to include AWS Lambda, a serverless computing platform and also announced availability through the AWS Marketplace.
-
Microservices to Not Reach Adopt Ring in ThoughtWorks Technology Radar
Whilst microservices come with many benefits over traditional monolithic applications, they can also introduce additional complexity into an organisation, writes Rebecca Parsons, chief technology officer at ThoughtWorks. Because of these tradeoffs, she does not believe that microservices should always be the default architecture choice for a software application.
-
Q&A with Bob McWhirter on WildFly Swarm Rename to Thorntail
In early 2015, Red Hat released Wildfly Swarm, which allows Java EE based applications to run as microservices. The approach allowed developers to migrate Java EE monolith applications to microservices by creating an uber-JAR that not only contains the Java program but embeds its dependencies as well. Wildfly Swarm was recently renamed to Thorntail.
-
Microservices and Site Reliability Engineering
A recent article talks about how the complexities introduced by microservices initially seem at odds with the concept of Site Reliability Engineering (SRE), and how companies such as Google are tackling that to ensure that whilst development groups can continue to embrace microservices, they and their SRE teams have the necessary tools and understandings to make them work well together.
-
Cloud Native Java Has A New Home: Jakarta EE
Mike Milinkovich, executive director at the Eclipse Foundation, introduced a new Eclipse governance model and roadmap for Jakarta EE at this year’s JAX conference. Based on a recent survey of over 1800 Java developers, the new governance model will focus on support for cloud native application development and faster release cycles. Milinkovich spoke with InfoQ on the future of Jakarta EE.
-
The Future of Microservices as the IT World Changes: Uwe Friedrichsen at microXchg Berlin
You have finally mastered Microservices, including Docker and Kubernetes, and some other new cool trends. But are you prepared for the future, Uwe Friedrichsen asked in his presentation at microXchg 2018 in Berlin where he explored the future of IT and the consequences for microservices.
-
Designing Reactive Systems Using DDD, Event Storming and Actors
Domain-driven design (DDD) is often used for finding boundaries (bounded contexts) around microservices. But everything in domain-driven design (DDD) is not good for microservice, Lutz Huehnken claimed in a presentation at microxchg 2018 in Berlin where he discussed how DDD, Event Storming and the Akka-based Lagom framework can be used to build reactive systems.