3 ms·
Wow, very cool indeed. We worked on an open-source community[1] tool using Datomic/Codeq[2], and the ops portion was/has been pretty unpleasant. I'd love to see
by sgrove 13y ago
Wow, very cool indeed. We worked on an open-source community[1] tool using Datomic/Codeq[2], and the ops portion was/has been pretty unpleasant. I'd love to see Datomic-as-a-Service popup, even as a only-meant-for-starter-projects, just so that experimenting with it could be that much easier. That might be possible with the new license, depending on how the Cognitect team sees it.
[1] The service is a frontend to Codeq, having imported many Clojure repos: http://www.jidaexplorer.com/ http://www.jidaexplorer.com/
[2] http://blog.datomic.com/2012/10/codeq.html http://blog.datomic.com/2012/10/codeq.html
EDIT: Added links.
- drcode 13y agoYeah, a Datomic service would be soooo nice.
- dustingetz 13y agoI would like to know more about datomic from an ops perspective if you feel like elaborating?
- cgag 13y agoYes, same, I think a lot of people would be interested.
- sgrove 13y agoI would ask coolsunglasses as he's been using it in production for far longer in a bigger installation than we have.
- jeletonskelly 13y agoI've been working with Datomic, as a developer, in a production environment for the last 4-5 months. In terms of the work done by your ops guys, I'd say it really depends on how you're using it. Datomic has it's own AMI, which can be a hassle if you're used to rolling your own (which we ended up doing). I'd say one of the biggest challenges to overcome on the ops side is dealing with transactor failures. If a transactor dies, then the data from the peers will likely just fall on the floor. If you use DDB as a store, you have to keep an eye on your provisioning and scale appropriately.