[speed_spread]

Running costs or development costs? If you have a low-request / high complexity persistent application you may want to optimize for maintainability. Having all the code in one place _can_ make things easier to figure out in the long term.

[thatwasunusual]

> Running costs

Running costs.

> Having all the code in one place _can_ make things easier to figure out in the long term.

My experience is the exact opposite. A huge monolith makes it harder for developers - especially new ones - to get a grasp of how everything is connected. A separation of concern into micro services is sometimes a good solution.

[0x445442]

Also there’s configuration management costs to consider, which usually ends up being a biggie.

[JAlexoid]

> maintainability

Sir this is HN, half of the people here will quit their team well before maintainability is even uttered.

[speed_spread]

In the words of a friend and former colleague: "shit fast, shit hard, and then leave"