What makes dapps "special" (i.e. why we have a separate name for them) is that they utilize a blockchain in one way or another. For example for storage or transfer of data.

I think the point is that's not actually an interesting feature. The programs use an over-hyped database hoping to siphon off a bit of the hype...did we have a separate name for programs using NoSQL too?

Yes, blockchains _have_ been overhyped thus far. But there is some promise to having distributed control over a database.

For instance, you can build a company with [token|share]holders that no one controls -- a true cooperative. (full disclosure I work on this problem)

>have a separate name for programs using NoSQL too?

Yeah, horrible legacy projects that are a pain in the ass to maintain

Source: I am working on a legacy API based on a noSQL database with a very dumb design (because the data was relational of course) in a very large company

> Yeah, horrible legacy projects that are a pain in the ass to maintain

How can a "legacy" project be using noSQL? In my company, "legacy" projects are projects that have been around for 10+ years. MongoDB hasn't even been out a full 10 years, yet...

>How can a "legacy" project be using noSQL?

A project doesn't need to be 10+ years old to be legacy.

This API is 3y old, and was the first iteration, the v1, of the company's digital asset management API, it's only maintained for a few teams around the world, whereas the v2 is well crafted and has a way more logical datamodel

Legacy != old

It's just weird when I read stuff like "Yeah, I've had to do a bunch of maintenance on our legacy webpack/Angular 2 system" because in my mind webpack and Angular 2 are still very recent technologies, just not recent compared to webpack 2/Angular 5