[zug_zug]

>> 4. Don’t just seek architectural consistency

I don't know what the author has in mind, but I plainly disagree when stated as a general rule like this.

Examples: Try to get every server on the same OS by default, same packages, standardized networks, health check at the same path, prefer the same port, deployed with standard jenkins jobs, use a standard versioning scheme, use the standard branching model, standardize logging, standardize error-handling, standardize datastores, use standard login/security.

[nelsondev]

That’s “Dev Ops” consistency, not architectural consistency.

Insisting on architectural consistency might mean every service needs to use a relational database, and have an exposed API. But a pub/sub or map reduce, may not fit neatly into that architectural model.