Dom-top Alternatives

Similar projects and alternatives to dom-top

kit

34 447 8.0 Clojure dom-top VS kit

Lightweight, modular framework for scalable web development in Clojure (by kit-clj)
biff

29 723 8.9 Clojure dom-top VS biff

A Clojure web framework for solo developers.
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
honeysql

16 1,705 8.6 Clojure dom-top VS honeysql

Turn Clojure data structures into SQL
clojure-graph-resources

6 252 1.8 dom-top VS clojure-graph-resources

A curated list of Clojure resources for dealing with graph-like data.
elle

5 614 8.5 Isabelle dom-top VS elle

Black-box transactional safety checker based on cycle detection
Korma

1 1,476 10.0 Clojure dom-top VS Korma

Tasty SQL for Clojure.
history

1 7 6.2 Clojure dom-top VS history

Support library for working with Jepsen histories (by jepsen-io)
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better dom-top alternative or higher similarity.

Suggest an alternative to dom-top

dom-top reviews and mentions

Posts with mentions or reviews of dom-top. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-06.

Why Is Jepsen Written in Clojure?
8 projects | news.ycombinator.com | 6 Dec 2023

Nope! For a few reasons Jepsen sticks very closely to Traditional JVM Threads.
Part of that is because Jepsen isn't hyper-concurrent. Most concurrency errors manifest in just a handful of client threads, and the JVM will run ~10K threads without too many issues.
Another part is that I spend a lot of time debugging and profiling. Core.async turns stacktraces into Swiss cheese--it has to, to perform its implicit continuation-passing magic. But that can make it really hard to figure out Who Called What When, and Why Is This Process Slow. Standard blocking IO calls are also something that my profiler (YourKit) can analyze well.
Finally, I invest a lot of time into tuning Jepsen for speed, and manage the handoff of data between threads carefully. In a system where actors were handing off state constantly core.async would be a bigger help, but there's really only a couple shapes for concurrent handoff in Jepsen, and they're addressed by either j.u.c. queues, forkjoin-style structured concurrency, or Weird Transactional Threadpool stuff.
For a little more on this, take a look at https://github.com/aphyr/dom-top or https://github.com/jepsen-io/history/blob/main/src/jepsen/hi...