You really can get all the benefits of popular architectures without going off the rails! Don't start out with a DI framework, use poor man's DI (ie 'passing s

You really can get all the benefits of popular architectures without going off the rails! Don't start out with a DI framework, use poor man's DI (ie 'passing stuff in'). Don't start out with microservices, use (poor man's) DI, ban all public static/global variables, and segregate code into separate processes with public 'interfaces' (but don't use actual interfaces until you actually need them! 1 interface per class is an antipattern!). These can all run in an async process pool you build, which can monitor bottlenecks when you get to that point. You can then (years later) easily break an internal service into a microservice when the trade off makes sense. I'm obviously static typing/oop focused, but there's a version of this which applies to any paradigm.