#Software-Architecture
13 notas · última:
Avoiding Identity Obsession in .NET with Entity Framework Core
Peter Ritchie shows how to configure EF Core shadow properties so a database-required primary key never leaks into a Domain-Driven Design entity's own model.
Micro And Macro Software Architectures, Why You Need Both
Draws the line between macro architecture decisions a company makes once for everyone and micro architecture decisions each team makes for itself, and argues both need to be explicit.
Cross-App Communication with RPC in Elixir
How Gearflow connects two Phoenix apps over distributed Erlang RPC instead of HTTP, and the coupling trade-off they accepted to skip building an internal API.
EP130: Design a System Like YouTube
Covers eight Software Development Life Cycle models and a 9-step pipeline for a YouTube-like video system, from upload through transcoding to CDN delivery.
EP118: What are the differences among database locks?
A five-topic system design refresher: database lock types, six pagination techniques, MVC-family architecture patterns, what happens on a URL request, and QR code payments.
Did contexts kill Phoenix?
Argues that Phoenix's contexts layer, meant to enforce domain-driven boundaries, raised the barrier to entry enough to slow the framework's adoption relative to Rails.
Understanding Pure Domain Modelling
Argues that domain experts default to describing their existing system rather than the real domain, and proposes asking 'what would you do without a system?' to get past that bias.
Refactoring to Serverless: From Application to Automation
AWS engineers propose 'serverless refactoring': moving logic like event publishing out of application code and into automation code (CDK, Lambda Destinations) to separate business logic from topology.
From Microservices to Modular Monoliths
Argues that teams stuck in microservice hell should migrate back to modular monoliths, keeping modularity without distributed-system overhead.
Architecture Is a Game of Constraint Satisfaction
Gregor Hohpe argues architects keep designing around constraints (procurement lead times, hardware size, coupling costs) long after the constraint that justified them has quietly disappeared.
The Publish Pattern
A concurrency pattern for decoupling producers and consumers using a const shared_ptr, avoiding mutex bottlenecks while keeping the consumer always on the latest published version.
Four Layer Architecture
A pattern from the c2 wiki splits client-server apps into View, ApplicationModel, DomainModel and Infrastructure, extending MVC to cover persistence and the outside world.
33/60 Days System Design Questions
A daily.dev system design prompt: an order service that only stores current state can't reconstruct a billing dispute, and the post argues event sourcing is the real fix, not a patch.