8 posts tagged ADR. See all posts
AI across the software development lifecycle, from requirements and architecture to coding, testing, deployment, operations, security, and compliance. Practical guidance on AI authority, deterministic controls, human ownership, and safe engineering workflows.
This week: a practical guide to 10 ADR anti-patterns with concrete examples showing how to write architecture decisions that actually help your team. Uber shares two infrastructure deep dives — making OpenSearch zone-failure resilient with isolation groups and forced shard allocation awareness, and GitFarm, a Git-as-a-Service platform that delivers full monorepo checkouts in under 500ms. And Dropbox traces the decade-long evolution of Riviera from file preview service to a universal content processing platform now powering AI ingestion at 2.5 billion requests per day.
In this article, I will explain 10 anti-patterns in Architecture Decision Records and how to avoid them. Consider this article a guide to following Best Practices and creating a good Architecture Decision Record (ADR).
Prepare for your next .NET interview with 800+ interview questions and answers covering C#, ASP.NET Core, SQL, NoSQL, microservices, distributed systems, testing, AI, Agile, desktop and mobile development. For developers, senior engineers, architects and tech leads.
AbstractLess: Approach to avoid complexity in your system architecture
Weekend Reading: A weekly roundup of interesting Software Architecture and Programming articles from tech companies. Find fresh ideas and insights every weekend.
Learn how Frugal Architecture helps you build cost-efficient, scalable, and sustainable software systems. Discover practical tips, rules, and common pitfalls to optimize your architecture for better performance and lower costs.
Explore essential techniques for effective software architecture documentation, including Architecture Decision Records (ADRs), Requests for Comments (RFCs), Event Storming, the C4 Model, and Non-Functional Requirements (NFRs). Learn how these methods help maintain, scale, and evolve your system architecture while ensuring clarity for both technical and non-technical stakeholders.