Recent posts tagged microservices

Why publishing an event is only the beginning of building a reliable distributed system. Building an event-driven application with Spring Boot is relatively straightforward. You create a Kafka producer, publish an event, implement a consumer, and p...

Shared storage provides the source of truth. Local caches provide speed. Events help keep cache state in sync. Project: Polar Bear Cache — GitHub repositoryhttps://github.com/babyblue94520/polar-bear-cache In my previous discussions about microser...

Sync Session: Rethinking Session Management in Microservices Project: Sync Session on GitHubhttps://github.com/babyblue94520/sync-session Shared storage provides the source of truth. Local caches provide performance. Events synchronize session sta...

Microservices improve deployment flexibility, but they also create a larger HTTP attack surface. Public APIs, authentication services, administration panels, checkout endpoints, and internal services exposed through an ingress layer may all receive t...

Microservices expand delivery flexibility, but they also create more HTTP entry points, routing paths, and service boundaries to review. A practical WAF strategy begins by deciding where external traffic should enter the system and which applications...

A customer clicks Place order. Your API returns success. The order row is in the database. But the service that processes orders never sees an event. This is not a hypothetical edge case invented by Kafka. It is a failure window in a common Spring B...

⚡ EDA ≠ Just Pub/Sub: Building Flexible Request/Reply Journeys Through Event Choreography > 🚀 Exciting Update: Incredibly honored that this deep dive was selected for the HackerNoon Science Tech Brief within 12 hours of its original release! Sharin...

Stop Wasting Days on Dev Setup: How We Automated Our Microservices Environment for Every Developer How we reduced new developer onboarding from 3 days to 15 minutes and eliminated configuration drift across 12 microservices. The Problem That Mad...

I recently needed something small: a POST /api/contact endpoint for my portfolio site at https://www.isaiah.name.ng that takes a name, email, and message, validates it, and emails it to me. The kind of thing you'd normally knock out without thinking ...

Modern applications rely heavily on APIs. But networks are unreliable - requests fail, time out, or get retried. Now imagine this scenario: User clicks “Pay Now” Request sent to server Payment processed successfully But response is lost due to ...

What is the Circuit Breaker Pattern? The Circuit Breaker Pattern is an architectural design pattern used in software development to detect failures and encapsulate the logic of preventing a failure from cascading throughout a system. It works by wr...

In modern software engineering, building a reliable system isn't just about preventing errors; it is about managing them gracefully when they occur. The Circuit Breaker Pattern is a design pattern used in software development to prevent an applicatio...

Service Mesh Zero-Trust Architecture Zero-trust is a property that emerges when several independent checks each verify a request on their own, without assuming the layers around them already did the work. It often gets described as a product you in...

The circuit breaker pattern is a modern software design strategy used to detect failures and prevent an application from repeatedly executing an operation that is highly likely to fail. It acts as a protective wrapper around external calls, monitorin...

What is the Circuit Breaker Pattern? The Circuit Breaker Pattern is an architectural design pattern used in software development to detect failures and encapsulate the logic of preventing a failure from cascading throughout a system. It works by wr...

After tackling the question of which branching strategy is best/blog/continuous-delivery-office-hours-e3, we turn our focus to architecture in this Continuous Delivery Office Hours episode. In particular, we discuss how big your building blocks shoul...

Tony Kelly hosts our latest episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton. Your system's architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a stick...

How to move from isolated hospital systems to event‑driven, FHIR‑based architectures in a context with poor connectivity and legacy vendors. In many private clinics in Venezuela, “digital transformation” has meant installing a Hospital Information S...