Fork me on GitHub
Oliver George02:12:55

Hello. Can someone clarify how licensing works for developers. I think each registration is allowed one license for Datomic Starter with 1 year of upgrades. Does that mean each dev on my team will be unable to access a current version of Datomic Starter for development purposes after 1 year?

Oliver George02:12:52

For example, I poked around with Datomic briefly in 2014 and I can't see any way to "renew" my starter license.


Do you have a great tutorial how to import logs with timestamps into Datomic? I saw I need to use :db/txInstant .. as when the transaction recorded.. just would be great an example. thx


{:db/id "datomic.tx"
 :db/txInstant #inst "2014-02-28"}]


What is the best case?


I believe the advice is not to use :db/txInstant to record the instant at which the observations within a transaction occurred, unless perhaps you have an irrefutable guarantee that you will never ever need to import your logs in any order.


thank you for your advice, how can I import large logs with ts in Datomic (sorry for the beginner question)?


it's about backup/restore?


I have a database (I can transform to json or any format, like a big log) and I would like to import to Datomic.


I would like to add new records to this db in Datomic


(timestamps very critical) / I don`t know.. it might be good if I use manual timestamps or maybe here is more elegant solution


no idea. 😕 But I'm also interested.


setting explicit txInstant on import is intended for this type of use


one second, i’ll get you the docs and an example


Ok, thanks!!


Note that you have to assert them in order, so you need to sort your source data in ascending time order


Datomic will not allow you to specify a txInstant that is older than the newest that already exists in the db


Ok! that is important! thank you very much!!


thanks @U05120CBV @U2J4FRT2T 👍👍👍

jaret19:12:21 @laujensen This section of docs covers updating a Datomic system. >To upgrade the transactor, start a new transactor (or pair of transactors) based on the release of Datomic you are upgrading to. Once these processes are up and monitoring the storage heartbeat, kill the old transactors and the new ones will automatically take over. >To upgrade peer applications, simply start new peers and take down old ones. You can stagger the ups and downs to maintain availability during the upgrade.


Does anyone have experience with using Datomic from a non clojure project? Say Java, Ruby, or NodeJS? Curious how your experience was. I used datomic in a clojure project on my last team and everyone loved it. I recommended it to my team, and they are really excited about the auditing capabilities Datomic provides. Its likely we won’t be using clojure though.


I’m interested in this too. Specifically node.js on AWS lambda via the client api


If I remember good then Datomic.. have Nodejs library, Ruby and Python. I don’t have experience.


The nodejs lib uses the (old) rest api, to use the new Datomic Cloud service, we need client api support. Nodejs has the best cold-start time for AWS Lambda so it is preferable.


I created in the past therefore a multi-route java lambda which in one “line” running like a logger (run automatically), in other 5-6 routes.. solved the cold start problems. In this way, system was faster.


that only helps the cold start from zero problem i.e. when scaling up under load, there are more cold starts that users will see


I’m pretty sure this use case is why the client API was created. Looking forward to an official client that works for a fast-starting lambda