zombodb VS nhost

And lots of interesting extensions use it, like

https://github.com/tembo-io/pgmq

https://github.com/zombodb/zombodb

https://github.com/supabase/pg_jsonschema

Point 2 is generally solvable via engineering effort and careful dedicated code. From the existing tools, PGSync is an open source project that aims to specifically solve this problem. ZomboDB is an interesting Postgres extension that tackles point 2 (and I think partially point 3), by controlling and querying Elasticsearch through Postgres. I haven't yet tried either of these two projects, so I can't comment on their trade-offs, but I wanted to mention them.

Curious, did you try zombodb? [https://www.zombodb.com/]

What about zombodb, do you think that quickwit has all the necessary APIs?

No. Haha. Was just the right name for https://github.com/zombodb/zombodb at the time. Software where the only limit is yourself!

Among other things in that thread, there's some discussion of aspects of ZomboDB with its developer.

(From the project's website[0], ZomboDB is a Postgres extension that enables efficient full-text searching via the use of indexes backed by Elasticsearch.

Lots more info in readme at the project's github[1]).

[0] http://zombodb.com

[1] https://github.com/zombodb/zombodb

> The hardest part of building any search engine is keeping the index up-to-date with changes made to the underlying data store.

This deserves mention, as it solves that problem: https://github.com/zombodb/zombodb

From the README:

> ZomboDB brings powerful text-search and analytics features to Postgres by using Elasticsearch as an index type. Its comprehensive query language and SQL functions enable new and creative ways to query your relational data.

> From a technical perspective, ZomboDB is a 100% native Postgres extension that implements Postgres' Index Access Method API. As a native Postgres index type, ZomboDB allows you to CREATE INDEX ... USING zombodb on your existing Postgres tables. At that point, ZomboDB takes over and fully manages the remote Elasticsearch index and guarantees transactionally-correct text-search query results.

I find other things also hard in search engines: dealing with the plethora of human languages and all the requirements we may have to processing them. A mature solution like ES therefor is almost a must in the more demanding cases.

Hi there! My name is Eric Ridge. I'm the developer behind ZomboDB (https://github.com/zombodb/zombodb). It's a rust-based system for creating indexes in Postgres backed by Elasticsearch.

You can read more about it on our GitHub repo, but basically it brings most of the power of elasticsearch’s searching and analytics abilities straight into Postgres.

Hasura ❌ (technically yes with Nhost)

Yeah, I knew of those, I think that's discussed often enough on the dotnet subs. Ory and Zitadel I knew too, but those provide just one thing, and are not native to dotnet. Altough I'll admit, stuff like nhost seem native to typescript but uses go projects under the covers as well.

You can use Nhost (100% open source): https://github.com/nhost/nhost/tree/main/examples/docker-compose

Both are built by us, yes.

Hasura Auth has 1M+ pulls on Docker Hub and we have JS SDKs for both Auth and Storage.

Code: https://github.com/nhost/nhost/tree/main/packages

Docs: https://docs.nhost.io/reference/javascript

Another reason for me to eagerly participate in this hackathon was to get started with nhost. I must applaud their commendable documentation. It was butter smooth for me to get started and immediately feel confident about how I wanted to structure the backend for my application. The option of providing custom hooks for the NextJS application is the cherry on the cake moment for me 😃. Additionally, the integration with Hasura console made it very easy for me to work with GraphQL API. Understanding user roles and permissions was something new that I learnt. I was able to customize authorization for a different set of users based on their roles.

This is a fifteen days long hackathon sponsored by NHost. You need to build a project using any of the tools from React ecosystem and NHost services and write a blog about it.

We have a Vue client available too: https://github.com/nhost/nhost/tree/main/packages/vue

OH, that's unfortunate. I hope it was resolved. If not, you can get help on GitHub (https://github.com/nhost/nhost) or Discord (https://nhost.io/discord).