seafowl

Currently we're thinking about how to best integrate Splitgraph and Seafowl in order to build a managed pay-as-you-go Seafowl, kind of like Fauna [2] for analytics.

Is my thinking right that seafowl possibly replaces both duckdb (with IOx) and superset (if there's a web front-end)?

To clarify, Seafowl itself can't be hosted statically (it's a Rust server-side application), but it works well for statically hosted pages.

I use seafowl hosted on Cloud Run for a side project for Swedish Real Estate data.

Or, a potential use case could be extracting internal data from your warehouse to Seafowl in order to build public applications that use it.

For example, we use it in Seafowl [1] for user-defined functions, so does ScyllaDB [2].

This is why we made the query API easily cacheable by CDNs and Seafowl itself easy to deploy at the edge, e.g.

Around a million rows, seafowl works great!

A few months ago I paired gcsfuse with Seafowl [0][1].

Where does seafowl fit in when I compare it with, say, data-stack-in-a-box approach, for ex: meltano + dbt + duckdb + superset [0]?

[0] Seafowl is an early stage open source database written in Rust.

You might like what we're building with Seafowl [0], which is an open-source, single binary database you can deploy to the edge for executing cache-friendly queries (so e.g.

Another idea: We have a newer project called Seafowl [1], which is an open-source analytical database optimized for running "at the edge," with cache-friendly semantics making it ideal for querying from Web applications.

We're currently doing a lot of work at Splitgraph to reposition the product around this "analytics at the edge" use case, with usage-based billing, eventually moving our query execution from PostgreSQL to Seafowl.

[0] You might be most interested in our recent project Seafowl [1] which is an open-source analytical database optimized for running "at the edge," with cache-friendly semantics making it ideal for querying from Web applications.

We don't have a SaaS version of this yet, so you'll need to host it yourself, but perhaps the next thing to try would be loading this data into Seafowl and querying it "at the edge" - I've been thinking about ways that we could package Seafowl along as an OpenResty module, which could allow for true "at the edge" use cases like querying IP data in your reverse proxy.

With Seafowl, the idea is different from what the modern data stack addresses.

We also have an API to export from Splitgraph to Seafowl, just need to add the button (this week).

Here's an example [1] multi-page site with Next.js and Seafowl.