> "small-ish backoffice systems that never has to be web scale".
Doesn't production use of Datomic by Nubank and Netflix (to mention just two examples) belie this assertion?
Having the working set present on app servers means they don't put load on a precious centralized resource which becomes a bottleneck for reads. The peer model allows app servers to service reads directly, avoiding the cost of contention and an additional network hop, allowing for massive read scale.
Newer releases have improved significantly in this area. It's now possible to understand perf implications with the addition of io-stats[1] and query-stats[2].
Free beer binaries are not mutually exclusive of Enterprise support agreements featuring all those things you mentioned above _for people that need that_.
At Reify Health, we are building a more creative healthcare system. We envision a world where every potential therapy, if safe and effective, is available to the patients who can benefit. We are well-funded and backed by Tier-1 venture capital firms. Our healthcare system relies on clinical trials to develop new (potentially life-saving) treatments for patients, but clinical trials continue to be slow, unpredictable, and expensive. Reify Health’s products help both the companies driving new clinical trials and the doctors, nurses, and researchers who care for patient participants.
Whether you're affiliated with Gitlab or not, it's kind of shitty to use someone's platform to push a competitor. Nothing in the terms of service forbids it of course and you're absolutely free to do so, but it just feels more ethical and grown up to extoll Gitlab's virtues by using Gitlab to host the content and link to it from HN. Putting it on Github is at least a tacit implication of its superiority along some axis, which—to my eye anyway—undermines your message.