InfoQ Homepage Microservices Content on InfoQ
-
Seven Hard-Earned Lessons Learned Migrating a Monolith to Microservices
Based on experience gained from several microservices migrations, these seven lessons can help you be successful and overcome or avoid common challenges.
-
Azure + Spring Boot = Serverless - Q&A with Julien Dubois
Microsoft seems to prove over and over again its focus on cloud and the Java ecosystem is the new normal. Even though Java has been amongst the supported languages for Azure functions for some time now, Julien Dubois experimented with Spring Boot and Azure to see what this combination means for Azure serverless computing. InfoQ reached out to him to explore further his experience on this topic.
-
From Monolith to Event-Driven: Finding Seams in Your Future Architecture
One of the challenges of migrating your system’s architecture is excluding non-desirable attributes and leaving the target state uncorrupted. An event-driven architecture and its related patterns, CQRS and Event Sourcing, are positioned well to introduce seams into the architecture that allow you to separate legacy and modern elements.
-
Principles for Microservice Design: Think IDEALS, Rather than SOLID
For object-oriented design we follow the SOLID principles. For microservice design we propose developers follow the “IDEALS”: interface segregation, deployability (is on you), event-driven, availability over consistency, loose-coupling, and single responsibility.
-
Building Effective Microservices with gRPC, Ballerina, and Go
gRPC is a relatively new implementation of the Remote Procedure Call (RPC) API paradigm. It can play a major role in all synchronous communications between internal microservices. Here we examine key gRPC concepts, their usage, and benefits of having gRPC as an inter-service communication by using a real-world microservice use case.
-
Running Axon Server in Docker and Kubernetes
Axon Server is an all-in-one solution for CQRS and ES applications written in Java for the Axon Framework. In Part 2 we continue by looking at the platform we run it on; in particular Docker and Kubernetes.
-
Resilience in Deep Systems
Deep systems, with multiple layers of microservices, have special challenges, and handling them requires the right mindset and tools.
-
The Opportunity in App Modernization
The twin pressures of servicing apps running in production and modernizing them to the cloud are putting stress on development and platform teams. App Modernization needs to scale and be made efficient through documentation, products and frameworks. This article looks at the reasons, and approach, to app modernization.
-
Project Helidon Tutorial: Building Microservices with Oracle’s Lightweight Java Framework
Oracle introduced its new open-source framework, Helidon, in September 2018. Originally named Java for Cloud, Helidon is a collection of Java libraries for creating microservices-based applications. Within six months of its introduction, Helidon 1.0 was released in February 2019. The current stable release is Helidon 1.4.4, but Oracle is well on their way to releasing Helidon 2.0.
-
Running Axon Server - CQRS and Event Sourcing in Java
Axon Server Standard Edition is an Open Source, purpose-built solution supporting distributed CQRS and Event Sourcing applications written in Java with the Axon Framework. Part one in this series discusses running it locally and explores aspects of Administration/Security and Configuration. It also discusses more advanced features available with the Enterprise Edition - Clustering/Multi-Contexts.
-
Adoption of Cloud Native Architecture, Part 2: Stabilization Gaps and Anti-Patterns
In this second part of cloud native adoption article series, the authors discuss the anti-patterns to watch out for when using microservices architecture in your applications. They also discuss how to balance between architecture and technology stability by not reinventing the wheel in every new application and at the same time, avoiding arbitrary reuse of technologies.
-
The Past, Present, and Future of API Gateways
The edge has evolved from simple hardware load balancers to a full stack of hardware and software proxies that comprise API Gateways, content delivery networks, and load balancers. In this article, we’ll trace the evolution of the data center edge as application architecture and workflows have evolved.