TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Datomic Best Practices

120 pointsby Spendar89almost 10 years ago

3 comments

mattjaynesalmost 10 years ago
I have a client that is exploring Datomic, so I wonder if some of you can chime in on why this is popular at the moment and what your experiences are with it?<p>I&#x27;m a big Rich Hickey fan. If you don&#x27;t know who he is, he&#x27;s the guy behind Clojure and Datomic. I don&#x27;t use those tools, but his views on simplicity are wonderful.<p>Here&#x27;s a great quote of his on the subject:<p>&quot;Simplicity is hard work. But, there&#x27;s a huge payoff. The person who has a genuinely simpler system - a system made out of genuinely simple parts, is going to be able to affect the greatest change with the least work. He&#x27;s going to kick your ass. He&#x27;s gonna spend more time simplifying things up front and in the long haul he&#x27;s gonna wipe the plate with you because he&#x27;ll have that ability to change things when you&#x27;re struggling to push elephants around.&quot;<p>Here&#x27;s his classic talk on simplicity if you haven&#x27;t seen it yet: <a href="http:&#x2F;&#x2F;www.infoq.com&#x2F;presentations&#x2F;Simple-Made-Easy" rel="nofollow">http:&#x2F;&#x2F;www.infoq.com&#x2F;presentations&#x2F;Simple-Made-Easy</a>
评论 #9852398 未加载
评论 #9851211 未加载
评论 #9851547 未加载
评论 #9853393 未加载
评论 #9851149 未加载
评论 #9851254 未加载
评论 #9851583 未加载
trengrjalmost 10 years ago
Anyone willing to share their views on using Datomic in a production environment?
评论 #9851357 未加载
评论 #9852194 未加载
评论 #9851248 未加载
nickpsecurityalmost 10 years ago
It&#x27;s an interesting database. Regarding closed source complaint, it&#x27;s part of a false dilemma that keeps repeating unnecessarily: that one must choose open + free or closed + paid. Nonsense! You can have open source and proprietary licensing simultaneously. You can even let paying users extend it as Burroughs did for MCP OS in 60&#x27;s. I go into more detail here [1] on various models of source sharing and security review implications (my focus).<p>So, he could patent any key technology, publish the implementation with copyright protection, give source&#x2F;binaries to customers on condition they keep paying, let users extend it for internal use, and even let users submit such improvements for others to use.. His company continues to make money on the licensing in each of these cases. All of this has been done before. If anything, the real risk is on the users that the source license might change like what happen with QNX. It&#x27;s why I advocate perpetual licenses for a given release at a given rate which are re-issued each year a client pays.<p>[1] <a href="https:&#x2F;&#x2F;www.schneier.com&#x2F;blog&#x2F;archives&#x2F;2014&#x2F;05&#x2F;friday_squid_bl_424.html#c6051639" rel="nofollow">https:&#x2F;&#x2F;www.schneier.com&#x2F;blog&#x2F;archives&#x2F;2014&#x2F;05&#x2F;friday_squid_...</a>