examples VS SQLBoiler

For all the code and instructions of how to clone and run this example locally, see the Clerk Example in the Encore examples repo.

Encore is designed to work well with sqlc and is a simple method of trying it out, as Encore will take care of provisioning your databases automatically. Check out this hello-world example app using Encore and sqlc on GitHub.

Keep building with these Open Source App Templates.👈

To keep things simple, we're going to clone a pre-made backend app from Encore's template repo. It's a simple monolith implementing a URL shortener. The app has a REST API and a PostgreSQL database.

If you want to build something more, check out Encore's templates library for inspiration.

There's much more to Encore! If you want to get a feel for it, consider creating a free account and build an app with a template.

Download the elevenlabs package directory from https://github.com/encoredev/examples/tree/main/bits/elevenlabs and add it to the app directory you just created.

Keep building with these Open Source App Templates. 👈

You can see the end result code on GitHub here.

Thanks! Encore does support dropping down to plain HTTP requests which lets you use Websockets, see [1]. We hope to make it more ergonomic and less boilerplate-y in the future, but it is supported :)

[1] https://github.com/encoredev/examples/tree/main/websocket-ec...

SQLBoiler takes a database-first approach, generating Go code from your database schema. This means it creates highly optimized and custom-tailored code for your specific database schema. SQLBoiler is great for applications where the database schema is well-defined and changes infrequently. However, like sqlc, it requires regenerating the code when the database schema changes. It's well-suited for projects where performance is a key concern and the database design is stable​.

Moved all my projects to https://github.com/volatiletech/sqlboiler.

sqlboiler

My current ORM of choice is Bob [GitHub Link] which I created based on my experience using and maintaining SQLBoiler [GitHub Link].

You mean like ORMs? * sqlboiler: generates Go ORM using database schema.

SQL code generator (aka inspect a database or SQL files to generate data models). You have the option of using something like volatiletech/sqlboiler which looks at the a physical database and generates code based on the schema. Or SQLC which is an amazing and fast project.

After trying a half dozen migration engines for NodeJS, I was pleased to see Prisma and its excellent documentation. As a golang developer I am partial to SQLBoiler and its database-first approach, though perhaps this is a condition of our community where we want all the knobs. Prisma was code-first but still gave me enough control to feel confident.

I use sqlboiler which generates an ORM from your database, and sql-migrate which is a tool for managing SQL migrations. Although you have to write your migrations in SQL, which IMHO is a plus.

FWIW, the other posts point to https://gobuffalo.io/ and https://github.com/volatiletech/sqlboiler as possibilities.