@Daniel > I would be very interested in learning about how to use replikativ: > what can and can't it store, when is and isn't it a good fit, > demo/sample code of common and not so common use cases etc > I've looked at replikativ and even went down the "learn lots about > CRDTs" rabbit hole and think I have an OK understanding of the > theory, but I'm still not sure when and how to actually use > replikativ. Although it's probably best to assume not everyone in the > audience is familiar with CRDTs, so should probably include a brief > primer.
Sure, recently there was a CRDT presence inclusion into the Phoenix web framework for Elixir. So this would be to have simple backend replication. I agree that the vision is still too broad for concrete applications. I have mobile applications in mind, but Clojure for Android doesn't work with core.async atm. The idea is to use it like a simple in process Java-HashMap etc. For websites and node it works with cljs, but still has some rough edges. Would this be interesting for you? @Ashish > Thanks for replikativ and asking suggestions. I would like to also > know about general problems (both of domain and language) you faced > while developing library, and how / how not clojure helped you ? Ok. I guess this would be core.async error handling, kv-protocol with konserve and hasch for crypto, stackwise. Helpful was the decomposition of the stack and the ability to build a cross-platform stack with core.async. Most parts were missing though, because usually people build backends on top of JVM functionality/libs. In general as this is a data management system, Clojure is a fitting language, but at some points the nested untyped maps caused difficult debugging. I think this will be better with spec now. On what level would you expect these arguments? @Christopher > > Would love to see this talk (embarrassed I still haven't watched the > video you posted in Gitter though...). > > As you'd suspect, I'm definitely like to see a good bit on > DataScript/Datomic. Aside from that, I think a good focus on the > strengths and weakness (/challenges/work-to-be-done) would be very > informative, and help illustrate some of the implications of the > approach. In particular, challenges in dealing with larg(ish) data sets > and/or data that changes very frequently are very interesting. Indeed. Ok, good to know. I wish I already had closer look at datsync and how the two approaches could be integrated. Thanks for pointing out, Christian -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
