3 ms·

It's worth noting that Crux supports a healthy range of options for transaction log and document storage beyond Kafka, including a variety of JDBC backends (SQL

by refset 6y ago

It's worth noting that Crux supports a healthy range of options for transaction log and document storage beyond Kafka, including a variety of JDBC backends (SQLite, Postgres etc.) Kafka is usually more than most people want or need. There was a blog post recently about a new Firebase-like Clojure web framework which uses Crux + Digital Ocean's managed Postgres service: https://findka.com/blog/migrating-to-biff/ https://findka.com/blog/migrating-to-biff/ Disclosure: working on Crux :)

yellowapple 6y ago
> including a variety of JDBC backends (SQLite, Postgres etc.) How straightforward would it be to add a new JDBC-based node implementation? I'm noticing that SQL Server is apparently missing, which is a bit of a shame given how many off-the-shelf products use it (and could therefore probably integrate with Crux if Crux did so, too).
- refset 6y ago
  It's usually no more than a day or two's work for us to get a new dialect figured out and to wire up CI tests with containers etc. It wouldn't be infeasible for someone new to Clojure to manage it about the same time also. The hard part is the SQL, not the Clojure. Fortunately there actually is SQL Server support already: https://github.com/juxt/crux/blob/master/crux-jdbc/src/crux/jdbc/mssql.clj https://github.com/juxt/crux/blob/master/crux-jdbc/src/crux/... ...and I'll make sure the full range of backends is made clearer somewhere. Good feedback!