Re: Perhaps - just perhaps -
Would you mind enlightening us further about what you know and they don't?
5 publicly visible posts • joined 26 Aug 2015
I bought a Meizu phone which runs the Flyme version of Android 6. It arrived totally Google free which I promptly remedied because the Google eco-system works so well. The Flyme OS came with everything you need, but I choose Google and I think that will also still be the choice of many when offered an alternative because of its rich user experience.
NoSQL no doubt has it's uses - horses for courses. But I'm not sure this article uses correct examples to expound its use in appropriate scenarios.
"using our user name example, both users pick the name they want. It appears to succeed, but actually only one user gets the name they want and the other is left with a puzzle – the system said they got their user name but now they can't log on."
- why use a NoSQL database for this functionality? It doesn't sound appropriate.
"Take for instance "Time To Live" in Cassandra, which makes your data disappear after a certain amount of time. This can give the developer the ability to add a feature to an application that would be painful in a traditional relational database if, say, a user uploaded photos that disappear after a certain amount of time."
- easy in a relational DB. Use a scheduled job that looks at the creation date of the BLOB.
"Then there are Maps, Lists, and Sets as fields in the table. These let the developer store many attributes under one field, for example users could have multiple email addresses in a field storing their user data. If you want, these can map on to your application structures, making persisting state easy."
- it sounds like you are using the DB as a bit box over a generic data model which is not best practice.
I'm not against NoSQL, but an article where it is being used to it's best advantage would be more interesting. Then tell us how it differs from doing the same in a relational DB / SQL.