System Design Codex·36wA Quick Guide to RabbitMQ
RabbitMQ is a message broker that enables asynchronous communication between applications by acting as a middleman. Messages flow from producers to exchanges, which route them to queues based on bindings and routing keys, where consumers can process them. The system supports different exchange types (direct, topic, fanout) for various routing patterns, providing decoupling, scalability, and reliability for distributed systems.
Foojay.io·38wMonolith vs Microservices in 2025
The software architecture landscape in 2025 shows a shift from microservices hype toward balanced, context-driven decisions. Developer experience and simplicity are driving many teams back to monoliths or modular monoliths, while Infrastructure as Code tools like Terraform make architecture changes more manageable. Enterprises are embracing the stability and traceability of monolithic approaches, prioritizing sustainability and clarity over theoretical scalability. The debate has evolved from choosing sides to making informed decisions based on team needs, organizational context, and long-term maintainability.
Awesome·37wThe complete system designs crash course
A comprehensive overview of system design fundamentals covering web protocols, load balancing, databases, caching strategies, messaging systems, scalability patterns, security measures, and fault tolerance. Explains key concepts like CAP theorem, microservices communication, horizontal vs vertical scaling, and practical applications through examples like URL shorteners and file storage systems.
LogRocket·34wWhy Go design patterns still matter
Explores how three specific design patterns can solve scaling challenges in Go microservices while maintaining code simplicity. The discussion focuses on practical implementation strategies that balance architectural complexity with Go's design philosophy.
Programming Digest·35wHow to Keep Services Running During Failures?
Graceful degradation is a design principle that allows systems to maintain essential functionality during failures by operating at reduced capacity rather than crashing completely. Key strategies include rate limiting to control traffic, request coalescing to reduce duplicate queries, load shedding to prioritize critical requests, retry mechanisms with jitter to prevent thundering herd problems, circuit breakers to isolate failing services, request timeouts to prevent resource exhaustion, and comprehensive monitoring with alerting for proactive issue detection.
Microservices.io·38wMicroservices rules #9: Develop observable services
Part of a comprehensive microservices rules series, this installment focuses on developing observable services as a critical architectural principle. Observability enables fast flow in microservices environments by providing visibility into system behavior, performance, and issues. The rule emphasizes the importance of designing services with built-in observability capabilities from the ground up, rather than adding monitoring as an afterthought.
Awesome Go·37wInside the Tech Stack of dblayer - Go, Next.js 15, Express & Beyond
A detailed breakdown of dblayer's modular architecture, which transforms PostgreSQL databases into secure APIs and applications. The platform uses Go with Fiber for the core API server, Express.js with TypeScript for dashboard management, Next.js 15 for the frontend, and separate background workers for async tasks. The tech stack emphasizes performance, type safety, and maintainability across multiple loosely coupled services.
Telerik·37wIntegrate Kafka with NestJS for Event-Driven Microservices
A comprehensive guide to building event-driven microservices using Kafka and NestJS. Covers setting up Kafka with Docker, creating producer and consumer services, implementing message patterns, handling retries and offset management. Demonstrates building an order processing system with two microservices that communicate asynchronously through Kafka events, including practical configuration examples and error handling strategies.
Hacker News·34wThe Rise of Hybrid PHP: Blending PHP with Go and Rust
Modern PHP applications can achieve high performance by integrating compiled languages like Go and Rust through extensions and FFI, rather than rewriting entire systems. This hybrid approach combines PHP's developer productivity with the raw speed of systems languages for performance-critical components. FrankenPHP's worker mode and Go extension capabilities offer up to 4x performance improvements while maintaining the monolithic architecture's benefits.
Programmers are also human·36wThat one guy in tech meetings
A humorous dialogue depicting a common tech meeting scenario where one participant repeatedly suggests buzzword solutions like microservices, Kubernetes, and Rust regardless of context, while others try to have a productive discussion about refactoring and system improvements.