3 ms·
Some background: I spent 6 years building customer Django sites; for the last 3.5 years I've been doing IoT. For many organizations, a headless CMS are going t
by wiremine 7y ago
Some background: I spent 6 years building customer Django sites; for the last 3.5 years I've been doing IoT.
For many organizations, a headless CMS are going to be more and more of a requirement, as more content is delivered to non-web or and non-mobile contexts. Some examples:
1. Shipping content into voice or chat bots.
2. Shipping content to embedded devices like touch screens on home appliances or factory machines.
Going beyond the separation of the data store and the presentation layer: A lot of people haven't yet felt the pain of using traditional relational data for these nontraditional channels. In voice and chat, for example, a knowledge graph is much more helpful than a bunch of relational data (or at least alongside relational data).
On the flip side of this all: my wife runs a blog, and I doubt she'll ever need more than Wordpress.
So, as usually, pick the right tool for the problem.
- forgottenpass 7y ago>A lot of people haven't yet felt the pain of using traditional relational data for these nontraditional channels. Haha. Wow. I didn't know it was already time for another anti-relational hype cycle.
- wiremine 7y agoYou misunderstand. Relational isn't going away, it just isn't a solid fit for all forms of knowledge. Google's knowledge graph is a good example of a what I'm talking about, and that's about around 2012. It's used to power the assistant, for example. It's similar to how data warehouses aren't going away, but a lot of companies aren't trying to shoehorn _all_ their data star schemas. So if "relational databases aren't for everything" is hype, sign me up?