Best of Architecture — March 2025
- 1
- 2
Javascript developers·1y
Frontend Clean Architecture - (Reactjs, Nextjs)
Simple React project structure based on Atomic Design and Clean Architecture principles, aimed at organizing folders for scalable projects. No error handling, authentication, or logic included, just a clean setup to start faster.
- 3
- 4
ByteByteGo·1y
EP156: Software Architect Knowledge Map
Becoming a Software Architect involves mastering programming languages, gaining proficiency in essential tools, understanding key design and architectural principles, and acquiring knowledge in platforms, data analytics, networking, and security. Supporting skills such as decision-making, communication, and leadership are also crucial for a well-rounded skill set.
- 5
Container Solutions·1y
Why I'm No Longer Talking to Architects About Microservices
Microservices discussions are often unproductive due to unclear definitions, abstract conversations disconnected from business goals, and lack of necessary organizational changes. Instead of focusing on microservices as an end, it's crucial to address concrete challenges like faster feature deployment, reducing system coupling, and scaling efficiently. Effective microservices implementation requires cross-functional, autonomous teams and a mature DevOps culture. Organizational change is harder than software change and essential for microservices' success.
- 6
Netguru·1y
API Design Patterns: Best Practices for Building Scalable Interfaces
Learn best practices for designing scalable, secure, and user-friendly APIs by following proven patterns. Understand fundamentals, RESTful principles, API architecture, endpoint definition, data handling, and ensuring security with rate limiting. Strategies for efficient integration, performance, and developer-friendly internal APIs are also covered.
- 7
The Miners·1y
REST, RESTful APIs, and API documentation A dive-in on the most used architectural style to communicate between modern web applications!
REST (Representational State Transfer) is an architectural style used for designing network-based applications, particularly web APIs. It provides a set of constraints that improve the scalability, performance, and manageability of software systems. RESTful APIs use standard HTTP methods for CRUD operations and ensure stateless communication, promoting separation of concerns. Key constraints include client-server architecture, uniform interface, statelessness, cacheability, layered system, and optional code-on-demand. Clear and consistent documentation is crucial, and tools like OpenApi and Swagger can help in documenting APIs effectively.
- 8
Community Picks·1y
Writing useful Documentation
Effective documentation is crucial for onboarding new developers, clarifying product usage, and fostering communication among teams. The post offers strategies for understanding and meeting the needs of your audience, ensuring accessibility, getting feedback, and maintaining terminology consistency. It also highlights the importance of structure, narrative, and diagram clarity. Documentation should be treated as a continuous product, not a one-time project, and can benefit from automation and integration with codebases.
- 9
Collections·1yEraser AI: Automatically Updated Diagrams for Your Codebase
Eraser AI is an advanced tool that creates live, intuitive diagrams directly from your codebase, ensuring they stay up-to-date with minimal effort. It offers features such as automated diagram updates, intuitive visualizations of infrastructure and system architecture, and enhanced documentation. Proven to generate over 2.5 million diagrams in two years, Eraser AI significantly improves code comprehension and team collaboration.
- 10
Architecture Weekly·1y
Whole Architecture Weekly content is free now!
Architecture Weekly, a previously paid newsletter, is now entirely free, including all past articles and videos. The author, Oskar Dudycz, made this change to reduce personal pressure and focus on other work. Readers can access numerous articles and webinars on various topics and follow the YouTube channel for more content.
- 11
.NET·1y
Naming is hard, maybe the architecture you are using is not an architecture at all
The post challenges the common misuse of the term 'architecture' in software development, highlighting the distinction between system-level structures and code organization patterns. It argues that terms like Clean Architecture and MVC are patterns for organizing code, not the physical structure of a system. Clarifying this distinction can improve communication and design decisions in software development.
- 12
BitLemon·1y
How Virtual Memory Actually Works Behind the Scenes
The post explains how virtual memory works behind the scenes, focusing on the structure and function of page tables and the role of the memory management unit (MMU). It covers how page tables are used to map virtual memory to physical memory, the fields within page table entries, and how the MMU manages memory requests and translations. The post also discusses the translation lookaside buffer (TLB) and its function in speeding up address translation.
- 13
InfoWorld·1y
How to implement idempotent APIs in ASP.NET Core
Idempotent APIs ensure applications are robust, reliable, and fault-tolerant by preventing duplicate requests caused by network issues or client-side errors. This guide explains how to implement them in ASP.NET Core, with a focus on making HTTP POST methods idempotent through custom logic. The process involves assigning unique keys to requests, checking for these keys on the server side, and ensuring requests are processed only once. Code examples are provided for creating such APIs in ASP.NET Core using Visual Studio 2022.
- 14
Milan Jovanović·1y
How .NET Aspire Simplifies Service Discovery
.NET Aspire simplifies the development of distributed applications by employing a configuration-based approach for service discovery. This method reduces the complexity and maintenance associated with traditional service discovery methods. In addition, it offers seamless integration with the .NET ecosystem and supports scalable solutions like API gateways with YARP.
- 15
Microservices.io·1y
Microservices rules #7: Design loosely design-time coupled services - part 1
Microservices rule #7 focuses on designing loosely design-time coupled services, a key principle for effective use of microservices. This part explains the concepts of design-time coupling and cohesion, highlighting the benefits of loose design-time coupling. Future parts will cover how to design such systems and detect tight coupling.
