50. Arch Principles: The Common Principles

    đź’ˇ

    We’re exploring the fundamental ideas that shape software architecture. We’ll see how each principle addresses a real-life development problem, and how these principles unify to keep our system robust, testable, and aligned with actual features.

    1. Vertical Boundaries

    Real-Life Problem

    Your team needs to implement a “MakeOffer” feature in an application. You start coding domain logic in a shared “utils” folder, a controller in a separate “controllers” folder, database access in a random “db” folder. Soon, nobody knows where all the “MakeOffer” code is. People keep missing pieces or duplicating logic in weird places. The system becomes spaghetti…

    Let's resend your copy of the đź“•
    Enter your email that you used to purchase it with.

    Howdy đź‘‹

    This is an online wiki about the main topics over the last 40 years of software design, architecture & testing. It was created by Khalil Stemmler.

    This wiki's mission is to help eliminate the unknown unknowns, helping you get up to speed on the best practices and principles to write testable, flexible, and maintainable code.

    I created this wiki while I was connecting the dots on my own path. You can read more about that learning journey in the introduction

    Already bought it?

    If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.

    Want access?

    You can read the intro to the book for free and visit solidbook.io to buy the book/wiki! To get an idea of my writing, read some of my best free content here and here.

    Need help?

    Something not working? Have a question? You can reach me on at khalil@khalilstemmler.com.