InfoQ Homepage Microservices Content on InfoQ
-
How Shopify Migrated to a Modular Monolith
Kirsten Westeinde, senior engineer at Shopify, discussed the evolution of Shopify into a modular monolith at Shopify Unite 2019. This included using the design payoff line to decide when to make this change, how it was achieved, and also why microservices were ruled out as a target architecture.
-
High Scalability Workflow Engine Zeebe is Production Ready
Zeebe is a workflow engine designed to meet the scalability requirements of high-performance applications running on cloud-native and event-driven architectures, and to support workflows that span multiple microservices in low latency, high-throughput scenarios. Zeebe 0.20.0 has just been released as a free community edition and is considered production ready.
-
restQL V3 Released
The latest version of restQL, a microservices query language, has been released, providing notable new features including content aggregation, support for additional HTTP methods, self-healing functionality, and a version for node.js apps. Comprehensive performance improvements have made the latest version up to twice as fast as its predecessor.
-
Mistakes and Recoveries When Building an Event Sourcing System
When Nat Pryce and his team started building a system based on an event sourced architecture, they made a couple of significant mistakes in the design, but managed to recover from these mistakes with an ease that surprised them. In a blog post, Pryce describes the mistakes they made and the factors that made it possible for them to refactor the architecture and recover from their mistakes.
-
API Strategies at eBay
After working with improperly versioned SOAP-based APIs for many years, eBay decided to move to new RESTful APIs with semantic versioning and a deprecation standard. Focus is on extensibility and adaptability to make it easier for developers to create new applications that utilize eBay’s APIs. In a blog post, Tanya Vlahovic describes the concepts and how they are implemented in their APIs.
-
Defining Bounded Contexts — Eric Evans at DDD Europe
A bounded context is a defined part of software where particular terms and rules apply in a consistent way, Eric Evans explained in his keynote at DDD Europe earlier this year; it should have a refined model and a language with unambiguous definitions. In a recently published presentation, he describes different kinds of bounded contexts, including some that involve microservices.
-
Service Mesh Interface (SMI): Q&A with Microsoft's Lachlan Evenson
InfoQ caught up with Lachlan Evenson, principal program manager at Microsoft, regarding the recent announcement at KubeCon of the Service Mesh Interface (SMI). Topics also discussed included the ecosystem of service meshes on Kubernetes.
-
Solo.io Announces Service Mesh Hub and Chaos Engineering Tool
Solo.io, a cloud native software company, launched the first industry service mesh hub. The hub provides resources to help users adopt service mesh technology in hybrid and multi-cloud environments and features tools such as Istio, Linkerd, Envoy, AWS App Mesh, and HashiCorp Consul.
-
Experience Building Distributed Systems and Microservices — Jeppe Cramon at Micro CPH
We must understand the business domain we are working in, identify the bounded contexts and the business capabilities, and design our services using this knowledge. In a presentation at Micro CPH, Jeppe Cramon talked about his experience working with distributed systems, microservices and the principles and patterns he sees as beneficial for successfully creating microservices based systems.
-
Experiences Going from Event-Driven to Event Sourcing: Fangel and Ingerslev at MicroCPH
At MicroCPH 2019, Thomas Bøgh Fangel and Emil Krog Ingerslev, both at Lunar Way, a fintech company, described how after building a monolithic Rails application they decided to migrate to an event-driven microservices architecture. During the migration they found some design issues and decided to move to event sourcing. In their presentation they discuss the problems and how they solved them.
-
Allegro Launches Hermes 1.0, a REST-based Message Broker Built on Top of Kafka
Allegro has launched version 1.0 of Hermes, a rest API based message broker built on top of Apache Kafka. Whilst not containing any new features, this first major version release is given to the current stable codebase.
-
Microservices Framework Lagom 1.5 with Akka Management and Support for Kubernetes and OpenShift
Version 1.5 of the microservices framework Lagom comes with Akka Management, a set of tools for operating Akka powered applications, and support for deployment with Kubernetes or OpenShift. The recently released version 1.5 is built on Play 2.7.0, Alpakka Kafka 1.0 and Akka 2.5.22 and also adds support for Couchbase and for gRPC through Akka gRPC.
-
Introducing Traffic Director: Google's Service Mesh Control Plane
Traffic Director is GCP’s fully-managed traffic control plane for service meshes that offers resiliency, load balancing, and traffic control capabilities. Traffic Director is currently available as a beta release.
-
Mature Microservices and How to Operate Them: QCon London Q&A
Microservices is an architectural approach to keep systems decoupled for releasing many changes a day, said Sarah Wells in her keynote at QCon London 2019. To build resilient and maintainable systems you need things like load balancing across healthy nodes, backoff and retry, and persistence or fanning out of requests via queues. The best way to know whether your system is resilient is to test it.
-
Build a Monolith before Going for Microservices: Jan de Vries at MicroXchg Berlin
Most developers don’t work at global large-scale companies like Netflix. Most developers work in much smaller companies with maybe up to 50 – 80 developers, Jan de Vries noted in his presentation at MicroXchg Berlin, where he argued that a properly built monolith in many cases is superior to a microservices based architecture. With a well-built monolith, it will also be easy to pull services out.