Unless you're explicitly looking to experiment with a specific technology or framework, I think its a good practice to start your implementation reasoning from

Unless you're explicitly looking to experiment with a specific technology or framework, I think its a good practice to start your implementation reasoning from a boring perspective. What this means for you personally will vary based on your skillset. However, if you can pull something off in an "engineering-easy" way, you can be wildly productive. With that said, you have to be smart and know when boring is not enough. 3-tier apps are great until complexity pushes them into gnarly monolithic messes that resist change. And with some sensible UX thinking adopting SPAs can push your user experience forward. NoSQL databases might not be the best choice as your primary datastore but might be a better alternative than materialized views (Graph databases are often utilized by some organizations as part of their secret sauce)