Are NoSQL DB's like Mongo or Dynamo still popular and viable options for a database? It seemed as if a year ago everyone was advocating for them. I see less of that now, but I don't see anyone giving me a legitimate reason not to use them either.
Ask HN: Is NoSQL Still the Wave?
1–10 of 12 posts
Re: Ask HN: Is NoSQL Still the Wave?
#2Ideally you choose a database carefully based on requirements, known and reasonably foreseeable. You should carefully consider what you gain and what you give up by choosing a non-relational database, because that probably sits at the core of the application. Don't just follow fads or worry about what seems popular at the moment.
Re: Ask HN: Is NoSQL Still the Wave?
#3I think that the hype has slowed down around NoSQL, much in the same way as it happens around most technologies.
There are still very solid use cases for Mongo/Couch/Dynamo/GraphQL/etc. it's just that the hype train of "use NoSQL for everything, even situations that are tailor made for row/column stores" has quieted some (there's still pockets of "OMG MAP-REDUCE ALL THE THINGS").
I think the combination of the drop in hype, along with the ability to see gains with things like PostgreSQL (and others) handling JSON blobs well has made people actually evaluate trade offs a little bit more sanely.
Re: Ask HN: Is NoSQL Still the Wave?
#4[deleted]
Re: Ask HN: Is NoSQL Still the Wave?
#5I think that the hype has slowed down around NoSQL, much in the same way as it happens around most technologies. There are still very solid use cases for Mongo/Couch/Dynamo/GraphQL/etc. it's just that the hype train of "use NoSQL for everything, even situations that are tailor made for row/column stores" has quieted some (there's still pockets of "OMG MAP-REDUCE ALL THE THINGS"). I think the combination of the drop i…
This is true. When pgSQL, SQLite and MySQL began to support JSON in 2015/2016 a the attractiveness of NoSQL databases - especially - of document stores seemed to diminish somehow.
Re: Ask HN: Is NoSQL Still the Wave?
#6I think generally speaking now the talk surrounding NoSQL involves the use case more often than not. And that's probabbly how it should be.
Plenty of situations out there where I hear about people using SQL and NoSQL nearly hand in hand depending on what you need to do.
I think the hype has quieted and they're just another tool as they should be.
Re: Ask HN: Is NoSQL Still the Wave?
#7I think that the hype has slowed down around NoSQL, much in the same way as it happens around most technologies. There are still very solid use cases for Mongo/Couch/Dynamo/GraphQL/etc. it's just that the hype train of "use NoSQL for everything, even situations that are tailor made for row/column stores" has quieted some (there's still pockets of "OMG MAP-REDUCE ALL THE THINGS"). I think the combination of the drop i…
This is true. When pgSQL, SQLite and MySQL began to support JSON in 2015/2016 a the attractiveness of NoSQL databases - especially - of document stores seemed to diminish somehow.
I wouldn't consider it too surprising; most document store type data was still most effectively backed by a structured column/row store system; and the major structured datastores implementing JSON support made it easier to use that in a single db structure instead of trying to get something like Postgres and Mongo to play together; although there are still many use cases for tiered datastores that use a combination of SQL and NoSQL system).
Re: Ask HN: Is NoSQL Still the Wave?
#8Ideally you choose a database carefully based on requirements, known and reasonably foreseeable. You should carefully consider what you gain and what you give up by choosing a non-relational database, because that probably sits at the core of the application. Don't just follow fads or worry about what seems popular at the moment.
What kind of requirements point to nosql?
Re: Ask HN: Is NoSQL Still the Wave?
#9Ideally you choose a database carefully based on requirements, known and reasonably foreseeable. You should carefully consider what you gain and what you give up by choosing a non-relational database, because that probably sits at the core of the application. Don't just follow fads or worry about what seems popular at the moment.
What kind of requirements point to nosql?
High Availability, known data retrieval patterns and high
volumes of read/write.
Re: Ask HN: Is NoSQL Still the Wave?
#10Still the wave? More like the endless summer: IMS remains an IBM program product, as it has been since 1969, though the license fee has gone up a bit.
There have been, and will continue to be, many ways to store and retrieve data without row-column relations or SQL. As others have noted, the key is to understand the application requirements, and to use the right tool for the job.