No, of course not. But the question is, do you need a database?

A database is a big proposition: transactions, indexes, query processing, replication, distribution, etc. A fair number of use cases are just "Take this data and give it back to me when I ask for it".

ES (or any other not-a-database) might not be a full-bore DBMS. But it might be what you need.

▲

immibis 8 hours ago | parent [-]

Rule of thumb: Whenever you think you don't need relational database features, you will later discover why you do.

The one thing relational databases don't have, that you might need, is scaling. Maintaining data consistency implies a certain level of non-concurrency. Conversely, maintaining perfect concurrency implies a certain level of data inconsistency.

	▲	9rx 7 hours ago \| parent \| next [-]
		The other thing relational databases don't have, that you are definitely going to need, is a practical implementation. You could maybe consider Rel if you have a particular type of workload, but, realistically, just use a tablational database. It will be a lot easier and is arguably better.
	▲	8 hours ago \| parent \| prev [-]
		[deleted]