Quantcast
Channel: Question and Answer » transaction
Viewing all articles
Browse latest Browse all 35

More scalable alternative to a transaction-per.request in a SQL+REST stack?

$
0
0

I’m new in web programming with SQL database. So please forgive my ignorance.

I’m using some modern framework to make a REST server with a SQL database. I’m using transaction only when I think I need it. But during the development I find out that parallel operation land me to dead lock and inconsistent data so I started to add more transactions in the SQL queries.

Going on with the dead lock paranoia I’m approaching the idea that each REST request should have been coupled with an SQL transaction.

This way is more safer but the database is locked until the request is responded and.. I’m looking for more scalable solution. Any hints on what should be the right way to handle this problem a part of using the paradigma transaction-per-request?


Viewing all articles
Browse latest Browse all 35

Trending Articles