Database Usage Debate
Comments debate the necessity and optimal use of traditional databases (especially relational ones) in application architecture, questioning if using a database is a mistake, when to avoid them, and whether business logic belongs in the DB or app.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Would be interested to hear more about your opinion on why using a database is a mistake.
A lot of effort to not use a regular ole database as a database... when you know, you could just use a database.
Use a relational db unless you know it won't work for your app and you can articulate why it won't work.
Hard to remember - some devs / architects I met at LGA conference are trying to reduce their internal app footprints and move to a database is not the cow nor yours model.
No database system is perfect for all use cases, that's why we have options.
You are advising application developers against using their chosen database optimally? I think it is not needed, I rarely see an application change its database.
The take is, just because you already have a database, it might not be the best place to but all your data.
Because you might as well just use an SQL database
Or just use a database instead of creating problems for no reason.
What do you mean? I don’t understand, how is using a database an architectural mistake?