databases VS starter

In the code ,we are using SQLAlchemy as our ORM(Object Relational Mapper) and Databases as our query builder.

MySQL is a powerful and popular database, and it's well-suited for use with Python. In the following section, we are going through how to set up a connection to a MySQL database in an asynchronous manner using the create_asynchrouns_engine function from SQLAlchemy. We'll also use the databases package and the aiomysql extra dependency. We'll also adapt the SQLAlchemy declarative approach to defining our users' table.

To take an example: I switched a service over from doing synchronous (plain def everywhere) to async (async def and await everywhere, with async DB, and saw… basically no performance improvement.

No, as I said, async db connection is the key. You can do that with SQLAlchemy using the databases library, but since you are not using SQLAlchemy it makes more sense to use the underlying db driver, aiomysql, directly.

Using the encode/databases library and forgoing SQLAlchemy's ORM

ormar is a mini async ORM for python. It uses sqlalchemy for building queries, databases for asynchronous execution of queries, and pydantic for data validation. You can create an ormar model and generate pydantic models from it.

works but there seems to be a difference between the regular slqalchemy syntax from what https://github.com/encode/databases/ is using in the docs?

I've been enjoying developing on top of PostGraphile. https://www.graphile.org/

Good starter: https://github.com/graphile/starter

I can add a column the the db, and my frontend gets that autimagically (in dev mode, it generates a graphql schema out of the db, and from that it creates composables for my frontend wiht graphql-codegen). On the frontend I use Vue 3, the starter is build with nextjs/react.

I learned so much about postgresql and RLS from postgraphile starter project: https://github.com/graphile/starter/blob/main/%40app/db/migr...

also the project is worth checking out ;)

I'm a fairly seasoned developer, but I've started contributing to a project (graphile-starter) where the core business logic is defined in PL/pgSQL functions and realized I have a lot to learn.

Someone called it: "hasura for adults”

It's highly customisable, works directly with postgresql row levels security and the performance is quite good. It has a custom GraphiQL gui to work on queries/mutations.

To really see how it all works together checkout the starter project: https://github.com/graphile/starter it has migrations, job queue, graphql-codegen etc.

Benjie (https://github.com/benjie) is one of the greatest maintainers I've ever seen!

Here’s a full stack, batteries included example: https://github.com/graphile/starter it doesn’t have mobile app yet but could be added relatively easily.

Postgraphile starter uses most of the same tech and has all the same functionality as far as I can tell, with the additional benefit of Postgraphile generating your GraphQL schema and resolvers instead of worrying them manually.

Check out the Postgraphile Starter and how it handles auth and sessions in a graphql api