devuo

It's going to take a massive amount of work to upgrade from 1.0 to 2.0. Don't do that to yourself. Just go with 2.0.

Are you honestly comparing Typescript verbosity with Java type verbosity? It's an absolute joy to work with Typescript in an IDE from JetBrains.

It's really "not" that complicated. Start by assuming by default that you will use an RDBMS, then:

1) Attempt to model a database schema that fully and completely supports said data. This will force you to get a sufficiently deep understanding of the domain problem and how it's different parts relate to one another.

2) Is there a part of the domain problem whose dynamic or unstructured nature cannot be properly represented on a fixed database schema and/or this unstructured piece of data must be performantly queried? Add a "companion" Document DB to your architecture.

3) Are there performance issues/requirements on a given part of your system and you need to hold volatile data such as a cache of processed data, or you need to efficiently handle user sessions across multiple machines, or even a queuing system for processing tremendous amounts of data coming in? The add a "companion" Key-Value DB to your architecture.

... And many, many other examples of other specialized NoSQL DBs could be added here, but you get the idea.

Summing up: Understand the data > Attempt to model an RDBMS schema that supports said data > Use proper "companion" DBs for whatever data that does not fit in a RDBMS.

For real.

There's not a problem with trying to build new things, quite the opposite. The problem is not so much with the creators but with the adoptees. Just because you're using something "new", that does not give you the right to say that whatever else someone is using that's not what you are using, shit. That and writing bullshit comparison articles between X and Y and proclaiming that X is amazing and you are lame and outdated if you are still using Y. If there's a profession that's as full of posers and hipsters this has to be it.

Why do people keep comparing Angular, a complete framework with React, which tackles only a subset of Angular? Also, the supposed architectural "benefit" of using React over Angular is absolute bullshit. You can have the same exact approach using Angular — the one with 50 different components — by building 50 different Angular Directives. I absolutely abhor when people make absolute statements about things to which they are completely ignorant about.

atm

Read D.T Suzuki "Essays in Zen Buddhism"

Completely agree. It's problem at the domain level, and not in REST per se.