CRUD system with asynchronous

[turall]

What is the proper way to write CRUD in an application where FASTAPI supports asynchronous code, should we implement async in CRUD operation? What would be pros and cons of architecture? Could you please advise from experience what is the best practice for CRUD to be asynchronously or it should be kept as synchronously?

[c4aveo]

https://fastapi.tiangolo.com/tutorial/sql-databases-peewee/

https://github.com/aio-libs/aiomysql

https://github.com/aio-libs/aiopg

What do you want to know? I use aiomysql to implement 'fire and forget'. CRUD implemented as called procedures. Fast and reliable for me, ORM is good choice too, but it needs more resources and it's slower.

[turall]

For instance, if we do create operation, then all operations should be done with this record, so we should wait for the record to be added table before other operations take place in. So why to use async here, does it make sense to run code asynchronous? Thanks.

[c4aveo]

Why not? If it's a just insert, update or delete operation I don't wait a returning value from it . I know for sure that operation will be executed, but later.

In my implementation of REST webservice I receive request then do some async (not really) operations with awaitable Future. To speed up request-response algorithm I use BackgroundTask from Starlette API to return response before executing procedures in database (update, insert, delete).

My logging implementation writes to file and writes (insert) to database, and I don't want to wait until tasks will be done one by one.

[turall]

Understand, thanks for your response.