This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-03
Channels
- # announcements (1)
- # babashka (2)
- # beginners (17)
- # calva (11)
- # cider (4)
- # clara (3)
- # clj-kondo (19)
- # cljs-dev (60)
- # clojure (27)
- # clojure-europe (1)
- # clojure-nl (2)
- # clojure-spec (1)
- # clojure-uk (11)
- # clojurescript (128)
- # core-logic (7)
- # cursive (7)
- # data-science (3)
- # datomic (76)
- # defnpodcast (4)
- # fulcro (5)
- # malli (5)
- # off-topic (7)
- # re-frame (1)
- # reitit (3)
- # shadow-cljs (86)
- # spacemacs (5)
- # test-check (48)
- # tools-deps (9)
- # vim (12)
- # xtdb (6)
What are trade-offs of using Crux as compared with Postgresql?
Hi 🙂 - there are a lot of angles to this, but I imagine the main reasons for seriously considering Crux over Postgres as things stand today are: - you need simple point-in-time bitemporal queries - you have a need for in-process graph-like queries - you want to use Datalog - you already use Kafka and you don't care for all the bells and whistles in Postgres enough to justify running an extra system - you would like to be able to extend or modify a small modular database that is written in Clojure I don't know enough about Fulcro to comment on that aspect. Any thoughts?
Fulcro is Clojure(Script) framework built on the top of React that uses EQL (similar in scope but more powerful than GraphQL) for it's language of communication with server. At server Pathom is used to parse Queries and Mutations sent from Fulcro client. Fulcro also helps with state management at frontend with it's normalised graph database and provides many other capabilities.
Thanks, that helps a lot. There's JDBC node too for Crux, what node option should I prefer? Can I start with JDBC node with PostgreSQL then change Crux node to Kafka when scale is needed? (without losing data).
It's most likely a question of what you have available to hand already and whether you have other potential use-cases for introducing either option into your stack. Migrating from JDBC/Postgres to Kafka when you need to scale is definitely plausible and desirable. You could use our Kafka connectors to do this replication
I'm interested to know because I want to use Fulcro for my application.
Thanks, that helps a lot. There's JDBC node too for Crux, what node option should I prefer? Can I start with JDBC node with PostgreSQL then change Crux node to Kafka when scale is needed? (without losing data).