connection pool storage options about database-kit HOT 2 CLOSED

For an example on sharing pooled connections across all event loops, have a look at
https://gist.github.com/MrMage/8972472ee73ab7b7d506ffb1c2b6e42e.

from database-kit.

This was for the most part implemented in #53.

Process:
Sharing connections across a process is not reasonable given Vapor's design. Each connection stores a reference to its event loop, which should always be the Request's event loop. This allows for route handlers to be much more efficient and not need to change threads a lot.

Thread:
There's a new ThreadConnectionPool type that, if shared across threads, will yield the same connection pool per thread.

Instance:
Initializing a new connection pool will not share storage with any other connection pools that have been created in the thread or process.

from database-kit.