Frameworks are implementation choices
Start with the product's traffic shape, security model, data relationships, integration boundaries, content needs, and operating environment. Those constraints narrow the useful options.
Optimize for the team that will own it
A technically impressive stack can be the wrong choice if it creates scarce skills, opaque operations, or unnecessary services. Maintainability is an architectural requirement.
Leave room to evolve
Good architecture creates explicit boundaries and avoids irreversible coupling. It does not attempt to predict every future feature or distribute a system before the scale requires it.