FYI: Question asked in Quarkus repo re FalkorDB support

[flowt-au]

Hi. Just a FYI. I just posted a question in the Quarkus repo about their intensions regarding FalkorDB.

Any thoughts from your side?

Thanks again,
Murray

[gkorland]

Redis COPY is not supported by FalkorDB only GRAPH.COPY see: https://docs.falkordb.com/commands/graph.copy.html

[gkorland]

Can't you use JFalkorDB?
https://github.com/FalkorDB/JFalkorDB/

[flowt-au]

Possibly, but I have written an entire database wrapper around RedisGraph (and now using FalkorDB instead) that leverages the Quarkus Reactive approach (ie using SmallRye Uni / Multi) and the Vertx Reactive Redis client, as mentioned. It works really well, except that now I want to start using the FalkorDB functionality that Redis (Vertx) knows nothing about. To use JFalkorDB I would need to work out how to wrap it with a Uni so it doesn't block the thread on the Uni pipeline. My Quarkus app is an API endpoint which builds a Uni pipeline for which FalkorDB is the "database" layer. I am sure that is possible but will be a big learning curve for me. And, if that is what it takes, so be it. I really like both Quarkus and FalkorDB and want to continue to use them together.

[flowt-au]

And maybe that isnt so hard

Uni<T> myAsyncMethod() {
    return Uni.createFrom().item(() -> {
        // Blocking third-party call
        T result = blockingThirdPartyMethod();
        return result;
    }).runSubscriptionOn(Infrastructure.getDefaultExecutor());
}

Anyway....

[gkorland]

I'm not that familiar with Quarkus, so I can't comment about your last comment. Does it work for you?

[flowt-au]

I am just about to start my day and will do some tests. If I can wrap JFalkorDB in a Uni then I can make a reactive FalkorDB client and use that instead of the Quarkus reactive Redis client. The upside of that is (apart from working with FalkorDB!) it will be more light-weight because it wont have the code needed to support the other Redis modules.

I will get back to you. Thanks!