HN Theater @HNTheaterMonth

The best talks and videos of Hacker News.

Hacker News Comments on
Rich Hickey on Datomic Ions, September 12, 2018

Clojure/nyc · Youtube · 147 HN points · 0 HN comments
HN Theater has aggregated all Hacker News stories and comments that mention Clojure/nyc's video "Rich Hickey on Datomic Ions, September 12, 2018".
Youtube Summary
The incidental complexity dragon never sleeps! In building Datomic Cloud we took on simplifying Datomic deployment, security and scaling on AWS, embodying and encapsulating best practices and maximizing connectivity to the AWS ecosystem. When you need to deploy your application on AWS you'll face similar challenges.

The idea behind Datomic Ions is to let you focus on writing your Clojure application and the ions tooling will get it running on your Datomic cloud nodes, without you having to run any other instances or become an AWS expert.

In this talk I'll explain the ideas behind ions, the Datomic cloud architecture and the ions tooling and application lifecycle model.
HN Theater Rankings

Hacker News Stories and Comments

All the comments and stories posted to Hacker News that reference this video.
Sep 17, 2018 · 147 points, 20 comments · submitted by alpeware
icey
This is about a feature of the Datomic database called Ions, which appear to be analogous to stored procedures (e.g. running Clojure functions in the db). From reading https://docs.datomic.com/cloud/ions/ions.html, that's an oversimplification, but I didn't know what it was so figured I'd save someone a search.
gw
Transaction functions were always part of datomic, even when running it outside of AWS. I think of Ion as a tool that wraps all the complex insanity of AWS so you can write an app as closely as possible to how you'd write a traditional Clojure app meant to run on a single server. In that sense it's not even specifically about datomic... You can even choose not to use it as your database, but of course then you'll be on your own as far as scaling your db.
Scarbutt
These is really nice for some, but on the other side, I'm worried the peer is going to be considered legacy.
lbj
In our experience Datomic has been quite the disappointment. Datalog is great, the rest is less so. Off the charts and unpredictable memory consumption, slow queries with no hope of optimization (we're talking 2.3seconds/100k rows) unexplainable dataloss. So many great ideas, sketchy implementation. Cant say if the Cloud version is better, we never tried.
lsb
That sounds like a valuable experience report to write up and link to!
Scarbutt
But they promise this new product (Datomic Cloud which is incompatible with traditional Datomic called on-premise) will solve all your performance issues because they have taken the work of doing all the AWS for you.
dgellow
I’m curious about the reasons someone would use Datomic. Did you just tried it out to evaluate it or did you have an actual use case for it? If you did have one, would you be okay to elaborate?
bhurlow
Out team chose Datomic for it's graph like properties and emphasis on data locality. This is optimal for GraphQL style patterns where you'd otherwise join a million tables
technion
It's extremely tied to the Clojure community. Odds are if you write the language, you'll be pointed in that direction, even if you ask for a recommended PostgreSQL library.

It's something I struggled with - I can get any language over the line here but it's got to work with our existing data sets.

None
None
None
None
vlaaad
There are indexed attributes, isn't it a hope?
moocowtruck
i'd like to second and third this experience
marknadal
I was very excited about Datomic as well, but disappointed it wasn't Open Source.

I decided to fix that + build something that combines my favorite features from Postgres, Mongo, Neo4j, Couch/Pouch, Riak, Cassandra, Redis, Rethink, Firebase, and MySQL! Lol, it has only taken me 4 years and ~ still not v1.0 yet but the Internet Archive (Top 300 site in the world!) and others are running us in production. So give it a try - it is all MIT/Zlib/Apache2 licensed ( https://github.com/amark/gun ), no crippleware "opencore", and fast (20M ops/sec for cached data, which Datomic also does, but IDK their benchmarks off the top of my head).

gargamel9
Oooops, you forgot the first rule of Datomic license: Thou shall not talk about the Datomic (un)performance!
ttwwmm
For the unfamiliar:

> The Licensee hereby agrees, without the prior written consent of Cognitect, which may be withheld or conditioned at Cognitect’s sole discretion, it will not: [...] (j) publicly display or communicate the results of internal performance testing or other benchmarking or performance evaluation of the Software; [...]

https://www.datomic.com/on-prem-eula.html

I.e., the Oracle approach.

stingraycharles
Yep, for how much they are involved in the open source community, it's fairly disappointing this is not allowed:

https://www.datomic.com/on-prem-eula.html

"[The licensee will not] (j) publicly display or communicate the results of internal performance testing or other benchmarking or performance evaluation of the Software; "

I wish they wouldn't do this, it seems that they simply do not want to talk about this topic, even though the reason people usually choose Datomic is not performance but rather its abstractions -- so why the hostile attitude?

RaleyField
> simply do not want to talk about this topic

I wonder if there are many respectable companies that don't allow you to post benchmarks. It's almost as if they don't have any confidence in their product that they have to resort to such extraordinary measures.

None
None
striking
Oracle, Microsoft. They're called "DeWitt clauses", after the researcher who first invoked Oracle's wrath after publishing benchmarks and finding them to be the slowest. Read on:

* more about DeWitt: https://en.wikipedia.org/wiki/David_DeWitt#The_%22DeWitt_Cla...

* an overview of database licenses with such a clause today: https://stackoverflow.com/a/12116865/1376005

* an essay discussing the legality of such clauses, with links to further material on/about them: https://www.dwheeler.com/essays/dewitt-clause.html

3rdAccount
I think they've said before that they don't want someone saying the performance sucks when it is really just a bad query or something else that isn't the databases fault...this is usually the reason why talking about performance is outlawed.
dwohnitmok
But an analogous situation holds for almost all performance benchmarks of any product right? That seems to be an argument against ever making any benchmarks public.
3rdAccount
I don't agree with it.
HN Theater is an independent project and is not operated by Y Combinator or any of the video hosting platforms linked to on this site.
~ yaj@
;laksdfhjdhksalkfj more things
yahnd.com ~ Privacy Policy ~
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.