Sign in Subscribe

Topic

Microservices

A collection of 4 issues

Embracing the “Let It Crash” Philosophy in Software Development: Why Controlled Failures Can Strengthen Your Application

In the world of software development, stability and resilience are top priorities. While many developers are accustomed to catching and handling every possible exception, there’s a growing school of thought advocating for a “let it crash” philosophy. This approach, widely adopted in systems like Erlang, encourages developers to let

A Comprehensive Guide to Structuring a Backend with BFFs: Using a Ride-Hailing Application as a Case Study

The Backend for Frontend (BFF) pattern is becoming increasingly popular in modern software architecture, especially for applications that serve multiple frontends, such as web, mobile, or even micro-frontends. In the case of a ride-hailing application where you must cater to different user groups — such as passengers and drivers — the BFF

Must-Know Resiliency Patterns for Microservices

When implementing microservices, one of the key challenges is ensuring resiliency — the system's ability to handle failures gracefully without impacting overall performance. Microservices, being distributed systems, face increased complexity and vulnerability due to the many interactions between services. Resiliency patterns offer strategies to make your microservices architecture robust and fault-tolerant.

Why I Prefer a Modular Monolith Over Microservices in Enterprise Environments

In recent years, microservices have become a popular architectural choice for building complex software systems. The promise of independent, scalable services that can be developed, deployed, and maintained separately is certainly appealing, especially in large enterprise environments. However, after years of working in various software development projects, I've come to