Good Architecture principles
Good Architecture principles:
SOLID;
Separation of concerns (SoC): separate your application into different sections, and each section will address a separate concern;
System Service Components should be business-focused. Security, communications, or system services like logging, profiling, and configuration should be abstracted in the separate components;
Single Responsibility principle: Every module for a single functionality;
Principle of Least Knowledge (Or Law of Demeter): An object should have limited knowledge about other objects;
DRY;
KISS;
Minimize upfront design: Only design what is necessary. YAGNI ("You ain’t gonna need it"). think Return for Investment (ROI);
Composition over Inheritance while Reusing the Functionality;
Identify Components and Group them in Logical Layers;
Define the Communication Protocol, Data Format between Layers;
Design Exceptions and Exception Handling Mechanism;
Naming Convention.
Last updated
Was this helpful?