odoyle-rules

A rules engine for Clojure(Script) (by oakes)

Odoyle-rules Alternatives

Similar projects and alternatives to odoyle-rules

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

odoyle-rules reviews and mentions

Posts with mentions or reviews of odoyle-rules. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-09.
  • Use of Posh for frontend development?
    9 projects | /r/Clojure | 9 May 2023
    If you're going down this route I'd second the recommendation for O'Doyle Rules. (Haven't used it since I switched away from SPAs altogether, but when I was investigating stuff in that space, O'Doyle appeared to be taking the "correct approach" from what I could tell.)
  • [Blog] The Web Before Teatime
    3 projects | /r/Clojure | 17 Jan 2023
    That's what this tiny library does https://github.com/oakes/odoyle-rules
  • [ANN] odoyle-rules 1.0.0
    1 project | /r/Clojure | 14 Oct 2022
  • Ideas for DataScript 2
    6 projects | news.ycombinator.com | 14 Aug 2022
    Reactive updates is the big one, in my opinion. DataScript is a triumph and arguably is the reason why so many note-taking tools (Roam, Athens, Logseq, etc) are written in Clojure. But there are so many cases where it would be nice to react when some set of entities is changed.

    I think what we need is to figure out how to combine DataScript with a rules engine. I'm wrote a rules engine and made a writeup that compares the two together: "Using O'Doyle Rules as a poor man's DataScript" https://github.com/oakes/odoyle-rules/blob/master/bench-src/...

    Subscribing to individual entities is nice but with a rules engine you have so much more fine-grained control over your reactions. And with the RETE algorithm this can be done efficiently. Most libraries in this space just ignore it and make their own ad-hoc solution -- an informally-specified, bug-ridden, slow implementation of half of a rules engine.

  • UIs Are Streaming Dags
    6 projects | news.ycombinator.com | 30 Apr 2022
  • Datalog for HTTP APIs
    3 projects | /r/Clojure | 27 Apr 2022
    Odoyle-rules lets you write rules (forwards chaining) engine that you can run on client and server. There are a couple ways you can twist that idea to achieve a more unified system.
  • Next Web
    2 projects | /r/Clojure | 30 Apr 2021
    I suspect it'd be too much of a mismatch to be useful, but i haven't thought about it enough. I think a more promising idea is to try implementing a database with o'doyle. I wrote about my first attempt here: Using O'Doyle Rules as a poor man's DataScript Right now it would be too inefficient for large data sets because it has to constantly rebuild its index but i think with some small changes i could improve that and basically turn o'doyle into a tool for creating databases that come with reactivity for free.
  • O'Doyle Rules - a Clojure rules engine for the best of us
    6 projects | /r/Clojure | 10 Feb 2021
    No doubt there's a runtime cost in joining the facts together, so naturally a system that lumps facts together into records (like clara) will have to do fewer joins, and should be faster. I figured out that i could at least deduplicate my joins with derived facts as i explained here, which ended up being a really big perf boost. But there's still a tradeoff, and one where almost everyone should favor flexibility, i think.
  • A note from our sponsor - WorkOS
    workos.com | 28 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic odoyle-rules repo stats
10
513
6.2
7 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com