
Microservices Design Principles

Think of traditional organizations in which business analysts, developers, testers, and operations staff operate in separate functional teams. These teams are dependent on each other at a very low level. Even though they may be working toward the same goal, they will inevitably have different priorities. They will also have different processes and
... See moreJim Highsmith • EDGE: Value-Driven Digital Transformation
Modularity is an indispensable foundation for Conway’s Law as well. That’s because modules are where we should capture critical communication and what is learned from it. At the same time, modules can save teams from smearing mud all over their solution space. Modules are used both as conceptual boundaries and as physical compartments.
Vaughn Vernon • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
Static coupling Represents how static dependencies resolve within the architecture via contracts. These dependencies include operating system, frameworks, and/or libraries delivered via transitive dependency management, and any other operational requirement to allow the quantum to operate.
Neal Ford • Software Architecture: The Hard Parts
static coupling analyzes operational dependencies, and dynamic coupling analyzes communication dependencies.
Neal Ford • Software Architecture: The Hard Parts
High static coupling implies that the elements inside the architecture quantum are tightly wired together, which is really an aspect of contracts.
Neal Ford • Software Architecture: The Hard Parts
Microservices: Patterns and Applications: Designing fine-grained services by applying patterns
amazon.com