1

You know how people rant about js frameworks; well the very same is true about nosql.

I thought let me broaden my horizon (pun intended) with a nosql db in my project.
So from Friday evening, I started off with ElasticSearch, which is pretty simple to get started, but apparently I need to understand it a lot better to use it as a primary data-store.
Then I stumble upon orient-db, was pretty exciting and learnt the apis/librarys but researching it a bit more to learn about the community; there is some bad-blood there.
Now I'm onto something called ArangoDB, think I'll stick with this; Any more time spent on this and I'll just give up on the project.

Comments
  • 2
    Mongodb
  • 0
    mongodb is pretty decent i guess with good community support and libraries. but its crazy simple to with in the beginning.
  • 0
    Elasticsearch should not be a primary data store. It is an excellent cache but it is not built "persistence first".

    MongoDB might write your data when you tell it to but it is not ACID compliant and cannot guarantee writes. For small applications and load, this is acceptable. For any serious data, the inadequacies bubble up quickly.

    If you care about your data, have good backups and use proper SQL databases.

    </soapbox>
  • 0
    @T3hbeowulf partially true. Mongo is ACID at a document level, and you could achieve transactions, but with a bit more work than in sql - like using processing queues.
  • 0
    rethinkDB is pretty good
Add Comment