One Size Does Not Fit All

Explore the nuances of software architecture in this 46-minute conference talk from GOTO London 2016. Delve into the concept that one size does not fit all when it comes to structuring software components. Learn about information hiding, separation of concerns, and the Single Responsibility Principle. Examine indicators of strong and weak cohesion, and understand the forces that drive separation in software design. Investigate common traits of microservices and explore real-world examples of different-sized components, from nano-services to medium-sized structures. Identify and avoid antipatterns such as decoupling illusion, anemic services, and unjustified re-use. Gain insights into effective software architecture practices and discover what truly works in creating scalable, maintainable systems.

Introduction
Commonalities
Just make things the right size
Information Hiding
Separation of concerns
Single Responsibility Principle
Cohesion in 00: Object Calisthenics
Indicators of strong cohesion
Indicators of weak cohesion
Forces for separation
Environments
Microservices - Common Traits
Example: Pricing Engine
Super-small, really micro, nano
Example: Product Detail Page
Small, micro
Example: E-Commerce Site
Medium-sized
Hierarchy & Rule Example
Antipattern: Decoupling Illusion
Antipattern: Anemic Service
Antipattern: Unjustified Re-Use
What works