i'm not trying to be bothered with futures right now until the async/await syntax is more stable - would have to change all libraries, etc. even though threads are in a sense less optimal than await, just using threads to make simultaneous DB requests which dramatically speeds up the time per request. because so many requests can be fired at once, i also use a connection pool which means way less expensive db connections being made and a limited number of them at once
i'm not trying to be bothered with futures right now until the async/await syntax is more stable - would have to change all libraries, etc. even though threads are in a sense less optimal than await, just using threads to make simultaneous DB requests which dramatically speeds up the time per request. because so many requests can be fired at once, i also use a connection pool which means way less expensive db connections being made and a limited number of them at once