sorenbs

I know you are half joking, but it would really be helpful to have ball-park pricing available. Are we talking Sun-level markups here, or how should we think about it? Given the enterprise sales contact form, I'm thinking yes, but I'd love to know for sure.

Thats great to hear. Would be scary if they experienced a full outage.

Also check out https://github.com/feldera/feldera in this space. And do read the paper - It's a cool addition to the Materialize approach.

It sounds like you are thinking of publicly listed companies which have to adhere to strict regulation, much different from privately held companies.

Even then, there are no guarantees. A company can simply be mismanaged and overvalued as we saw recently with this Danish airline: https://apnews.com/article/scandinavian-airlines-air-francek...

At Prisma, our long-term vision is to bring the kind of complex application data infrastructure that is common in the Java and .NET ecosystems to the TypeScript ecosystem, where great DX and quick delivery is a core expectation. That's what we call DataDX. Many companies share this vision for a better future, and by giving it a name, I hope we can make progress together faster.

For a thorough deep-dive on what we are all about, I highly recommend this book by Martin Kleppann: https://dataintensive.net/. And for a more hands-on example, take a look at this session from QCon: https://twitter.com/gunnarmorling/status/1709925808511529148

iCloud is build on FoundationDB. You couldn't build iCloud on Redis. Most people are not building iCloud though.

You'll need each sqlite db to be relatively small for this approach to work well. Probably well under 1gb. If you construct a clever way for many small sqlites to form a bigger whole, that could work really well! Is that along the lines of what you are thinking?

As an example, you could imagine each Notion document being a separate sqlite...

A different view on this is that relationships is a property of the data, not of the query. So it makes sense to represent that in a single place instead of repeating it for every query. Now, if multiple teams have differing understandings of what relationships are present in the data, they can go ahead and use separate Prisma Schemas.

Thank you!

Really happy to see all the activity at the new repo. For a while there I thought the project was dying...

Thank you!

I'll try to get something set up to compare performance of the two on the same machine.

As an aside - we are evaluating different streaming engines to power data projections for Prisma.io. Excited to see support for Debezium coming in v0.4.0.

Would be interesting to somehow make Arroyo run the Nexmark benchmark so we can clearly compare to Flink and DBSP: https://liveandletlearn.net/post/vmware-take-3-experience-wi...

This is a really exciting project! I recently learned about https://github.com/vmware/database-stream-processor which builds on a new theoretical foundation and claims to be 9x faster than Flink. It is also written in Rust, and there is a compiler from SQL to Rust executables. Can you comment on the differences?

The big concern around fishing gear is that it is specifically designed to catch marine life, so when it is lost or deliberately discarded in the ocean, it continues to kill for years for no reason at all.

The movie Seaspiracy makes this point in a very graphic way: https://www.youtube.com/watch?v=1Q5CXN7soQg

This fact-check runs through all the points of the video in 15 minutes: https://www.youtube.com/watch?v=s7QRLZp63Eo

We really need Japan on this map :-)

I am excited to share a map with my group of friends going skiing next winter. I used to create a Notion doc with manually annotated screenshots from google maps, much like you. But this feels way better.

FDB supports atomic operations that you can use to implement at least some of this very easily in a way that avoids the extra round trip and conflicts: https://apple.github.io/foundationdb/developer-guide.html#at...

Really excited to see this launch!

We use Axiom at Prisma for various things and love it. Happy to answer questions if anybody is interested. Either here or on email.

The Vanmoof bikes have automatic shifters. I don’t like them because they are unpredictable, and you feel the difference. It’s jarring. The Cowboy is single speed, which works pretty well because of the motor. That’s my preferred configuration. But at high speeds it does feel like I’m at a spinning class, and it sounds like this system could fix that.

European ebikes are also limited to a 250w motor. They must need much more to make this system work, so probably can’t be classified that way.

Most of us moved on to better terminology 4+ years ago. The only ones derailing conversations are grumps like yourself who refuse to get with the program. Why is this so important to you?

Prisma won't work with D1 out of the box. The primary limitations are:

- SQLite is traditionally embedded in an application, so Prisma interacts with it by mounting a file. Workers does not have a local filesystem, and D1 is exposed over the network through an API accessible from a Worker. Prisma will have to create a specific connector for D1. - Workers have a script size limit which is currently 1MB. My understanding is that Cloudflare will be increasing this in the future. We also have specific work to decrease the size of Prisma. Both of those will have to happen before Prisma could be used with D1.

Note that Prisma already support querying Postgres, MySQL, SQL Server and MongoDB from Cloudflare Workers through the Prisma Data Proxy, which will see a GA release next month.

We are also very excited about D1 as a way to bring a subset of data closer to users in order to deliver faster experiences. We hope this will be a way to bring the benefit of edge computing to larger organisations who cannot simply rearchitect everything to run on Workers.

Migrations have gotten better recently, but there are still cases where you need to follow the 12 steps very carefully: https://www.sqlite.org/lang_altertable.html#otheralter

Prisma Migrate can automatically generate these steps, removing most of the pain. I'm sure other migration tools can do this as well.

The year Germany reaches ~100% renewable energy for electricity, will also be the year they install the most renewable capacity in history. It is very unlikely that the year after will see 0 renewable capacity installed. Instead, prices will start to fall steadily, dramatically accelerating the electrification of remaining sectors.

Remember that both wind and solar follow very predictably cost-reduction curves. Starting a few years before 2030, electricity consumers will start to see reduced energy bills because of this.

This is factually incorrect. The winter issue in Texas was almost exclusively lack of winterization of thermal plants as well as a market setup that was unable to predict and react to the weather. Wind generated more electricity during the event than what was committed in the market, and as such had no negative influence.

Really cool project! I like this new trend of building SaaS products as open source, and still delivering a hosted free tier. https://cal.com/ is another example of this. And super proud that both are using Prisma!

This is really cool!

We (Prisma) would love to support this project in any way we can. You can find my email in bio if you are interested in a call :-)

Hi Alex!

Do you already have companies using this in production or maybe evaluating it? What language do you see most demand for?

For anybody interested in more examples, you can take a look at the Prisma VS Code extension. It was originally written 100% in TypeScript, but as most of our tooling is in Rust, we have started to move pieces over to Rust via wasm: https://www.prisma.io/blog/vscode-extension-prisma-rust-weba...

This is really cool!

Can Haystack be used to index structured data, or just text?

Is it required to use elastic as the backend, or can you use a simpler file-based or in-memory backend?

Prisma will launch a data proxy, as well as support for cockroachdb and Cloudflare workers early next year.