Do you write questions or answers on Stack Overflow?

We have a collection of tips and best practices to help you improve your contributions to the vast store of knowledge that many developers use daily. Help us make Stack Overflow better for everyone!
overflow.tips

#Turso works well with the Qwik web framework. We love how it's easy to express your frontend and backend code together for readability.

In this post, James Sinkala shows how to query Turso from backend code as part of building a newsletter manager:

medium.com/p/creating-a-n…

Hey! ChiselStrike (moved to @tursodatabase) wants your feedback on #Turso , our edge-hosted distributed database, and we're willing to dish out some swag for it.

The only Edge that Glauber missed here is Joe's Gaming.

ChiselStrike #Turso , our edge-hosted distributed database based on libSQL, kicked off a private beta this week. You can sign up at chiselstrike.com.

Want to see Turso in action? Watch this brief demo with Doug Stevenson 🔥:

youtu.be/-AyMsSybKig

Really great to get our edge-hosted distributed database in the hands of developers! Please sign up for the beta and let me know what you think.

SQLite is regarded as an embedded database, but this is what happens when you embed it into a process that talks HTTP and Postgres.

25 years ago I worked on a product where we implemented MSSQL triggers in C++, which was effectively using the database as a message queue. 🤢

Fast forward to 2023, and now we're putting code in triggers again, but for the right reason: low latency compute adjacent to data.

There's some really clever code gen going on here to build a bespoke #TypeScript client library for your ChiselStrike (moved to @tursodatabase) backend.

Implementing a backend with ChiselStrike involves routes that map HTTP verbs and URL patterns to functions.

What makes our routes special is that entity CRUDs are automatically atomic during execution.

⬇️ Learn more about routes in our docs. ⬇️
docs.chiselstrike.com/reference/rout…

This new #TypeScript SDK generator is a huge step up for the usability of ChiselStrike in web applications, especially SPAs. And it's built to work well with TanStack Query for your #ReactJS apps.

It was a lot of fun to work with the team on this one!

REST and CRUD work together, but they are not the same.

Let’s explore the difference!

App data modeling with ChiselStrike is as easy as writing a #TypeScript class entity. There are no tables and no JSON. Expressing relationships between entities is natural and typesafe, and CRUD APIs come for free.

⬇️ Read more in the docs ⬇️
docs.chiselstrike.com/reference/data…

Thursday December 8, GDG Cleveland will meet at Tech Elevator. Doug Stevenson 🔥 is giving a talk on Jamstack, and a brief history the history of the web that brought it here as the primary new architectural stack for new web projects.

gdg.community.dev/events/details…

Google for Developers Communities - North America

One of the defining features of ChiselStrike is its ability to do data modeling entirely through #TypeScript class definitions, giving you a typesafe data persistence layer easily accessible from your backend code.

(And we're extending this to your web frontend code as well!)

Our first major milestone of libSQL with #WASM user defined functions was released today as v0.1.0. Piotr Sarna gives a summary of this feature in this article, along with a tool to compile #Rust code:

blog.chiselstrike.com/webassembly-fu…

#WebAssembly #sqlite

Go from zero to REST in minutes!

Watch this brief intro to ChiselStrike with Doug Stevenson 🔥 to learn how to get started building a backend for your app with with only a few lines of code.

youtube.com/watch?v=H6sBM5…

Lines of code required to build a backend persistence layer for your app: zero

ChiselStrike now offers experimental support for data policies. But wait! Isn’t middleware enough to guarantee data is safe and compliant? In this post we’ll explore what data policies can do that middleware can’t.

blog.chiselstrike.com/why-middleware…

We have big plans for our fork of SQLite! Take a look at the list of open issues on GitHub to see where we're going. (Issues are listed in no particular order.)

Questions or comments? We welcome your participation.

github.com/libsql/libsql/…