It makes many db calls interspersed throughout synchronous code inside the application. Normally I would assume this is super slow and has many round trips (unless it's transparently committed to memory and batched to db later). I also don't see anything about connection pool management eg acquire and release.
Does this code work efficiently because it essentially gets compiled into a type of pseudo "stored procedure" that runs all the application code on the db and as such avoids those problems?
If yes, is that a scalability issue to have so much going on in a heavy infrastructure unit such as a db?
If no, then is there a perf issue here based on my initial assumption?
Specifically, `spawn_enemy` here: https://github.com/clockworklabs/BitCraftPublic/blob/master/...
It makes many db calls interspersed throughout synchronous code inside the application. Normally I would assume this is super slow and has many round trips (unless it's transparently committed to memory and batched to db later). I also don't see anything about connection pool management eg acquire and release.
Does this code work efficiently because it essentially gets compiled into a type of pseudo "stored procedure" that runs all the application code on the db and as such avoids those problems?
If yes, is that a scalability issue to have so much going on in a heavy infrastructure unit such as a db?
If no, then is there a perf issue here based on my initial assumption?