News for hackers. Stuff that matters.
Re:Migration from Postgres to Datomic by modarts on Thursday July 06, 2017 @09:11PM (#14715256)
This comes up every time Datomic is mentioned, but it's tremendously sad to see such a revolutionary technology lack any sizable adoption because of its licensing model.

Datomic packages up a CQRS + event-sourced architecture in a really nice way. You can stash graph/tree/relational/tabular/(insert shape here) data and query it out with the powerful Datalog language. You get time travel (versioning) for free. Etc, etc.

It's a crime that this hasn't taken off as one of the leading data stores; hopefully Cognitec has some sort of roadmap to an open source release.

Re:Migration from Postgres to Datomic by zcam on Thursday July 06, 2017 @11:44PM (#14715865)
Stuart Halloway said "Datomic is not and will not be open source" in the latest defn podcast, so don't hold your breath. Hopefully they change their mind. They seem to be focused on a cloud (managed?) solution offering at the moment.
Re:Migration from Postgres to Datomic by _xczx on Friday July 07, 2017 @03:42AM (#14716767)
Thats disappointing, because Datomic is not and will not be adopted. No one wants to revolutionize data back to postgres when cognitect goes out of business. Stable solutions are found in cloud hosting from too big to fail companies and self-management. However, maybe they have found a niche through people taking on risk for major technical debt.
Re:Migration from Postgres to Datomic by nine_k on Friday July 07, 2017 @12:09PM (#14719526)
Exactly.

I would only make a closed-source solution a centerpiece of my business if:

* The thing is known to work for a number of other people, and uniquely solves my urgent problem, while no open solution can't do anything comparable. This is probably the Datomic niche.

* The thing was around for ages, and is a cash cow of a major and reliable software maker, and is also significantly better than open software in some important area. This is how MS or IBM sell their databases; Datomic doesn't have nearly enough mindshare to compete here.

* I'm hastily building an MVP that I plan to scrap anyway when the growth hits / the startup is acquired. Datomic is likely too expensive for that.

By necessity, the first case holds for a small number of businesses.

Re:Migration from Postgres to Datomic by zcam on Friday July 07, 2017 @03:58AM (#14716836)
It probably pays the bills, I guess they're happy with it if that's still a thing after 5 years (?).

It's not helping clojure grow as much as it could though and it's a bit a chicken/egg problem, more clojure users could be more datomic users and vis-versa.

Re:Migration from Postgres to Datomic by jb1991 on Friday July 07, 2017 @05:34AM (#14717153)
Fortunately, at least if Cognitect does go out of business, the Clojure language would survive fine. Hence why Clojure with Postgres (a very common pairing) is by far the safest bet.
Re:Migration from Postgres to Datomic by Arcsech on Friday July 07, 2017 @10:15AM (#14718465)
That's very disappointing. While I don't begrudge Cognitect money, it's obviously possible to make money with an OSS database and I wish they'd gone that route. It's my opinion that your database is the #1 most important part of your stack to be open, as your data is the most important thing.

I've been considering trying to get up to speed with Mentat[0], which is a Mozilla project to create a Datomic-like layer over SQLite for desktop applications, and help out with that or even try to start a full open source clone of Datomic, though probably won't happen for a good while due to real life happening.

It's got so many good ideas and it sucks to see them go to waste in a proprietary database where basically nobody gets to use them.

[0]: https://github.com/mozilla/mentat

Re:Migration from Postgres to Datomic by treehau5 on Friday July 07, 2017 @10:35AM (#14718624)
> it's obviously possible

What if it's unobviously not possible?

Re:Migration from Postgres to Datomic by tosh on Monday July 10, 2017 @12:11PM (#14737209)
do you remember when in the episode they talk about this?

edit: found it https://soundcloud.com/defn-771544745/23-the-right-honourabl...

Re:Migration from Postgres to Datomic by dustingetz on Friday July 07, 2017 @10:07AM (#14718393)
Where can I find more about this cloud offering ????
Re:Migration from Postgres to Datomic by itchynosedev on Thursday July 06, 2017 @09:23PM (#14715313)
Hell, even implementing CRUD applications with Datomic / Clojure and Clojurescript is blowing everything else out of the water.

No string literals, pure data. Add transit to the mix and you get full-stack killer combo with unparalleled productivity.

With so many parts from Cognitect filling the stack it would be silly not to boost adoption with a friendly licensing.

Re:Migration from Postgres to Datomic by slagfart on Thursday July 06, 2017 @09:50PM (#14715444)
"Unparalleled productivity" sounds like hyperbole, especially considering the posts below, showing how exactly the same thing can be done trivially in Postgres.

Do you have an example?

Re:Migration from Postgres to Datomic by dustingetz on Friday July 07, 2017 @09:44AM (#14718239)
It's because Datomic doesn't have the object/relational impedance mismatch. Because immutbility yields idealized caching so a lot of hard performance problems inherent to RDBMS go away. It's like moving from CVS to Git.

Fuck it, hyperfiddle isn't launched but lets just post it here. Hyperfiddle is JSFiddle + Datomic. http://hyperfiddle.net/ If you care about this, you should reach out, please email me!

Re:Migration from Postgres to Datomic by vosper on Friday July 07, 2017 @10:13AM (#14718449)
It sounds like the site's not finished yet, but FYI it's a trainwreck on iPhone6 + Safari
Re:Migration from Postgres to Datomic by pbowyer on Friday July 07, 2017 @10:45AM (#14718713)
I like the idea. Nice work!
Re:Migration from Postgres to Datomic by joe-user on Thursday July 06, 2017 @11:30PM (#14715812)
This doesn't answer your question, but I just wanted to make clear that the posts below certainly do not show, trivially or otherwise, how to use "no string literals" and "pure data" in Postgres.
Re:Migration from Postgres to Datomic by iaabtpbtpnn on Friday July 07, 2017 @12:00AM (#14715935)
Those concepts don't make any sense, so it's no wonder that a serious RDMBS like Postgres doesn't support them.
Re:Migration from Postgres to Datomic by Risord on Friday July 07, 2017 @02:37AM (#14716540)
Can you explain your statement?
Re:Migration from Postgres to Datomic by narag on Friday July 07, 2017 @03:47AM (#14716791)
Can you explain what those concepts mean and why are they important? It's the first time I've read about them or Datomic for that matter.
Re:Migration from Postgres to Datomic by Risord on Friday July 07, 2017 @08:33AM (#14717845)
I asked since I don't know much about datomic either or how usable is it in production. So I haven't much to share.
Re:Migration from Postgres to Datomic by sheepmullet on Thursday July 06, 2017 @11:56PM (#14715913)
> especially considering the posts below, showing how exactly the same thing can be done trivially in Postgres.

So then where is the open source version / extension to Postgres?

How about this - I'll give you $1000 if you can give me a seamless extension on top of Postgres that has most of the functionality of Datomic.

Since it is trivial it is easy money for you.

Re:Migration from Postgres to Datomic by skrebbel on Friday July 07, 2017 @02:25AM (#14716483)
GGP talked about building a CRUD app with "unparalleled productivity". That's where the burden of proof is, not to the GP who is skeptical about that claim.
Re:Migration from Postgres to Datomic by VLM on Friday July 07, 2017 @08:28AM (#14717822)
"So then where is the open source version / extension to Postgres?"

As a concrete example I like the way in the datomic schema you can eliminate bridge tables for many-many relationships using :db/cardinality :db.cardinality/many and then you store or get a vector.

There should be a way to have a super-SQL middleware compatible with any language bindings including a bare CLI that eats "SQL plus some cardinality" and behind the scenes implements the bridge table manipulations. Don't repeat yourself and all that, and many/many tables are kinda repetitive.

There doesn't seem to be anything remotely like that out there.

Re:Migration from Postgres to Datomic by hellofunk on Friday July 07, 2017 @05:32AM (#14717146)
You are asking for evidence of disproof. That is a logical paradox, and frequently used as an argument by extremist politicians.

Where is the evidence that you do not [insert anything here]? That's a slippery slope of challenge.

Re:Migration from Postgres to Datomic by throw13209 on Friday July 07, 2017 @07:25AM (#14717582)
Unparalleled productivity maybe, but only once you've learned how to read code that looks like an AST, and to juggle parens in Emacs (learn paredit etc).

For better or worse, history has proven that doesn't appeal to many developers. Lisps just aren't popular, and that lack of mindshare matters.

Re:Migration from Postgres to Datomic by swlkr on Friday July 07, 2017 @07:02PM (#14722902)
There is parinfer which turns lisp into a white space significant language, no special commands necessary
Re:Migration from Postgres to Datomic by akmiller on Friday July 07, 2017 @10:12AM (#14718438)
I don't understand this line of thinking. The product is outstanding and likely will be, if it is not already, the lifeblood of Cognitect as a company (in conjunction with their consulting services I'm sure). What is wrong with a company building a worthwhile product to sell? This is a community (Hacker News that is) that should be in full support of companies building great products to sell!
Re:Migration from Postgres to Datomic by erichmond on Friday July 07, 2017 @11:20AM (#14719012)
I think it's fueled by a naive idea that paying for closed source software is inherently bad. Actually, it's not necessarily a naive idea, as this specific OP may have weighed the pros and cons and have decided that it's not worth the risk, but I do think there are very wrongheaded cargo cult ideas around this.

We tend to gloss over the fact that when dealing with OSS:

- Project maintainers can leave/change/stop supporting the software and the idea that "since it's OSS, I can just pick up the slack" sounds better in ones head, then it does in practice.

- Even large projects (think Angular) can move in odd and unexpected directions, which in reality simulate a company "going out of business" for all intents and purposes.

- OSS 'support' is great, until it's not. Meaning, if there are plenty of SO questions and answers, it's great, until your specific issue isn't addressed, at which point you're either looking to a third party to pay for support, or you're rolling your sleeves up and digging into a codebase you have no experience with outside of an external API level understanding.

The dirty secret of large successful companies is that they actually pay for software, and the support of that software because they understand that time = money and vice versa.

After using datomic in production, I'd welcome my competitor to use Postgres. I'd even push them to. It's a monstrous competitive advantage for me.

Re:Migration from Postgres to Datomic by zcam on Friday July 07, 2017 @11:27AM (#14719099)
There's more than just support to paid db services, look at neo4j, datastax, elastic, mongo and cockroachdb among others.
Re:Migration from Postgres to Datomic by nine_k on Friday July 07, 2017 @11:23AM (#14719048)
There is a "narrow niche" strategy, when you have a cool thing and only sell it to a small group of well-paying customers.

There is an "open" strategy, when you offer the core part of your cool thing widely (cheaply / freemium model / for free), and profit from only e.g. 10% of the users that buy premium plans. You also have a fair chance to make your better way of doing things predominant, and put in the hands of a lot of people that won't pay you either way.

The point is that when your cool thing may have a really wide adoption, with the "open" model you may have e.g. 50x the market share of the "narrow niche" model, and thus 5x the profit. Increased mindshare also helps further adoption. This, of course, depends on the adoption rate and paying customer rate.

Re:Migration from Postgres to Datomic by 0xdeadbeefbabe on Friday July 07, 2017 @12:15PM (#14719574)
> I don't understand this line of thinking.

Haven't you noticed the popularity contest going on with computing?

If datomic isn't popular it will disappear.

Re:Migration from Postgres to Datomic by mycat on Friday July 07, 2017 @05:53AM (#14717217)
Reminds me of Rebol. Technically as good as Lisp but arguably better as it is batteries included e.g. GUI. By the time the author made it open source it was far too late
Re:Migration from Postgres to Datomic by vosper on Friday July 07, 2017 @10:16AM (#14718471)
You might be interested in the Red language, which is an open source reboot of Rebol. It's actively developed, and has been for a while, although I think there are only a handful of people (one?) working on it.

http://www.red-lang.org

Re:Migration from Postgres to Datomic by juskrey on Friday July 07, 2017 @12:02AM (#14715942)
$5k per year is almost free comparing to average single coder compensation.
Re:Migration from Postgres to Datomic by zcam on Friday July 07, 2017 @03:15AM (#14716676)
The price is not really an issue. It could be $1 the problem would be the same.

It's essentially a black box now, you have no auditing possibility, no way to extend it, no guarantee you can pick up the pieces is cognitect/rich goes away. You basically sign a check, and hope for the better.

Re:Migration from Postgres to Datomic by SnootyMonkey on Friday July 07, 2017 @08:32AM (#14717844)
I'm sure price is still the issue. I bet for the right price Cognitect would be happy to provide the source to a customer.

Note: I too wish Datomic was OSS, just disagree that price isn't the issue. It is.

Re:Migration from Postgres to Datomic by vosper on Friday July 07, 2017 @12:19AM (#14716016)
Until they go out of business and you're fucked. That's when you wish you'd stuck with Postgres.
Re:Migration from Postgres to Datomic by pjmlp on Friday July 07, 2017 @02:11AM (#14716433)
Being closed for free doesn't mean it isn't open source for those that pay.

This was a common model before FOSS took off and it is still quite common in enterprise products.

If company X goes out of business you get the latest source version you paid for.

Having said this, I don't know if Cognitec has such kind of contracts.

Re:Migration from Postgres to Datomic by skrebbel on Friday July 07, 2017 @02:28AM (#14716497)
Going off topic here, but we have an enterprise lead for our SaaS product who is asking the same. They want some sort of warranty that they can keep hosting the product themselves, should we go bust. Going open source (or open core) is currently not an option for us.

Does anyone have any advice how to approach this? Example contracts, good experiences with escrow services maybe? Or bad experiences of course.

Re:Migration from Postgres to Datomic by twic on Friday July 07, 2017 @07:04AM (#14717487)
I worked for a company which sold hosted services in the financial sector. Escrow was a standard part of contracts. However, it wasn't taken immensely seriously; we faithfully put all of our source code into escrow once a year (or perhaps more often, but not as often as we released), but not all of the build, deployment, and infrastructure tools and config you would actually need to turn that code into a replica of the application. We didn't make any effort to "restore from backup" to verify that what was in escrow was actually any use. Customers, and their auditors, seemed happy with that.

I do feel that in a really well-run operation, your build, deploy, and operation should be so automated that that's just another set of repositories to put in escrow. One way to look at it is that escrow is just another kind of disaster recovery; if you have safe copies of everything you would need to restore your operations if you lost all your current servers, then it's easy to put those in escrow too.

Re:Migration from Postgres to Datomic by user5994461 on Friday July 07, 2017 @10:12AM (#14718443)
It's more meaningful for a shrink wrap software. It's easy to archive and handover the code repo, packages and documentation.

It's not really effective for saving a cloud hosting. A platform like that is not easily redeployable.

Re:Migration from Postgres to Datomic by skrebbel on Friday July 07, 2017 @02:06PM (#14720597)
Thanks. Do you know what escrow service that was?
Re:Migration from Postgres to Datomic by true_religion on Friday July 07, 2017 @05:06AM (#14717072)
It's difficult to do for SaaS since you're not already packaging up the product.

Datomic has perpetual free licenses so if they go bankrupt, you just keep the software you already have.

If you had an on-prem setup or a hosted white label solution, then it'd be easier to license.

Re:Migration from Postgres to Datomic by dragonwriter on Friday July 07, 2017 @09:55AM (#14718303)
> Being closed for free doesn't mean it isn't open source for those that pay.

True, but...

> This was a common model before FOSS took off and it is still quite common in enterprise products.

No, it wasn't and it's not. “Shared source” for paying customers was common before Free/Open Source Software (FOSS) took off (“Free” doesn't modify “Open Source”, they are essentially synonyms that identify the same license features but which are preferred by different ideological factions that prefer those features for different reasons.) Shared source does include access to the source, and it may include some rights to create derivatives (usually with no or restricted distribution rights), but it is not open source.

Re:Migration from Postgres to Datomic by pjmlp on Friday July 07, 2017 @12:08PM (#14719517)
Who cares about the religious meanings? What matters is having access to the code, whatever form it might be.

Also no one ever referred to it as "Shared Source" in the 80's.

Just to dig out one such product, here is the brochure of Turbo Pascal 5.5 from 1989.

https://archive.org/stream/bitsavers_borlandtur5.5Brochure19...

" Turbo Pascal 5.5 Runtime Library Source

Modify the runtime library source code or use it as it is. You get the assembly language and Pascal source code to the System, Dos, Crt, Printer and Turbo3 units. It comes with a batch file to help with recompiling and building TURBO.TPL."

For me, for my work, that was open enough.

Re:Migration from Postgres to Datomic by dragonwriter on Friday July 07, 2017 @12:13PM (#14719551)
> Who cares about the religious meanings?

It's no religion; the terms have well-established meanings.

> What matters is having access to the code, whatever form it might be.

The legal permissions you have to make use of the code very much matter, too. And those vary considerably among non-Open Source, source available/shared source license arrangements.

Re:Migration from Postgres to Datomic by pete23 on Friday July 07, 2017 @05:01AM (#14717057)
Source code escrow is standard for this sort of vendor contract.
Re:Migration from Postgres to Datomic by juskrey on Friday July 07, 2017 @04:27AM (#14716942)
The same can happen with every system, and the fact it is OSS won't help you much on practice. E.g. sqlite is signing >10 year contracts with some of their commercial clients which guarantee at least some level of professional support. Many clients won't even touch your software, regardless it is OSS or not, unless you can provide such kind of involvement.
Re:Migration from Postgres to Datomic by fnl on Friday July 07, 2017 @04:29AM (#14716945)
Or until they get bought up and shut their doors. Now where have I seen that one... :-)
Re:Migration from Postgres to Datomic by skrebbel on Friday July 07, 2017 @02:26AM (#14716490)
That's 2 programmer months where I live.
Re:Migration from Postgres to Datomic by nine_k on Friday July 07, 2017 @12:11PM (#14719536)
The licensing policy may be unfortunate.

The more important question is how many key patents are involved. That is, how feasible a comparable open-source project might be.