Splitting your app up based on "cognitive load" is just as bad a boundary as 100 LOC per microservice. It's an arbitrary measure and varies widely per developer

Splitting your app up based on "cognitive load" is just as bad a boundary as 100 LOC per microservice. It's an arbitrary measure and varies widely per developer. The most "correct" way I've ever seen applications divided is based on knowledge domains ala domain driven design (DDD). Drawing boundaries around the domain functionality of your business or operations means that the domain can be ignorant of other parts of your system.