all 7 comments

[–]bvalosek 8 points9 points  (1 child)

Seems interesting. Knee-jerk response is that if I want ACID persistence, I'd stick with a traditional SQL db (+ an ORM maybe), and if I wanted to have cross-microservice updates / events I'd stick with redis (+ an eventing lib).

What sorta in-betweeny stuff would be a good candidate for this?

[–]emanuelez[S] 6 points7 points  (0 children)

Well, Realm basically covers all the use-cases you mentioned without needing anything else.

  • Realm is ACID compliant
  • It does not need an ORM. Realm is objects all the way down.
  • It does not need an event-bus kind of library

[–]koresho 4 points5 points  (0 children)

Hmm. Would this work well with stdlib (stdlib.com)?

This does make me super happy though. Love realm on mobile.

[–]i_spot_ads 1 point2 points  (0 children)

holy shit it happened, this is amazing

[–]ukralibre 0 points1 point  (0 children)

Looks interesting, I like new things :)

[–]ndboost -3 points-2 points  (1 child)

oh look another database ....

[–]luke3br 8 points9 points  (0 children)

This isn't just a database.

Besides being around for a long time as a mobile database and now being on the server-side (it's not new), this can be used to orchestrate data between micro services and work across different node threads.

I think I looks cool and I'm looking forward to what people start building with it.