The First Object Database for Node: Introducing Realm Node.js
1–10 of 18 posts
Re: The First Object Database for Node: Introducing Realm Node.js
#2Re: The First Object Database for Node: Introducing Realm Node.js
#3Does this work with the new syncing stuff?
However, stay tuned more updates around sync very soon!
Re: The First Object Database for Node: Introducing Realm Node.js
#4Re: The First Object Database for Node: Introducing Realm Node.js
#5Re: The First Object Database for Node: Introducing Realm Node.js
#6What's the performance like? Hard to believe this could compete with SQL.
Re: The First Object Database for Node: Introducing Realm Node.js
#7Re: The First Object Database for Node: Introducing Realm Node.js
#8Realm is very cool technology, but the lack of a browser variant is a show-stopper for us. Our clients want web, iOS and Android versions of the apps we build. We really don't want to build our own CRDT syncing, I'd love to evaluate your stuff.
Re: The First Object Database for Node: Introducing Realm Node.js
#9Re: The First Object Database for Node: Introducing Realm Node.js
#10I think this would be particularly useful for Sandstorm applications. Since Sandstorm's grain-based model means that you have many small databases instead of a single big one (or a relatively small number of big shards), an embedded database like Realm seems like a particularly good fit here. I wonder if kentonv or any of the other Sandstorm developers have any thoughts on this.
Generally we like Sandstorm apps to use sqlite because it is well-optimized for the use case of a "small" (100k-1G) database on local storage with only one process accessing the database at a time. In this use case it doesn't make sense to have a separate process dedicated to the database, clustering is irrelevant, etc.
If Realm has similar properties then indeed it would work great for Sandstorm apps.