6 Quotes by Sam Newman

Robert C. Martin’s definition of the Single Responsibility Principle, which states “Gather together those things that change for the same reason, and separate those things that change for different reasons.

As developers, we often react badly when we see duplication. We worry about the extra cost of managing duplicate copies of information, and are even more concerned if this data diverges. But sometimes duplication is the lesser of two evils. Accepting some duplication in data may be a sensible trade-off if it means we avoid introducing coupling.

No matter how it looks at first, it’s always a people problem. Gerry Weinberg, The Second Law of Consulting.

The golden rule: can you make a change to a service and deploy it by itself without changing anything else?

When services are loosely coupled, a change to one service should not require a change to another.

If you are working in an organization that places lots of restrictions on how developers can do their work, then microservices may not be for you.