Support for serverless database drivers
As you dig deeper Engage with us on Let’s build amazing data-driven applications together Announcement Data Platform Don’t miss the next post Subscribe to the newsletter is now available Preview Released Jarrell Jon Harrell Jon Harrell is releasing preview support for the and serverless database drivers. This feature allows users to leverage existing database drivers to communicate with the database without the need for long-lived connections What is a Serverless Database Driver Traditionally database drivers establish long-lived connections with the database to communicate. Although the connection has some overhead initially there is almost no overhead for ongoing communication making it ideal for server deployments. But long-lived connections can cause problems.
In a serverless environ photo editing servies ment. Given the ephemeral nature of serverless functionality it can become a chore to keep track of connections, close idle connections, handle zombies and maintain an internal connection pool so the database doesn’t get flooded. In addition to this an increasing number of cloud providers do not allow arbitrary connections which makes it challenging to work with existing databases that rely on connections. Using a traditional database with serverless capabilities can quickly overwhelm the database. Serverless functions drain database connections quickly Serverless functions were developed in response to.
The above issues to provide a better experience for applications running on serverless functions. In addition, some database providers have also developed their own database driver libraries. These drivers use different protocols such as or instead of traditional connections and are therefore ideal for the rapidly evolving serverless world. So how do these serverless drivers fit in? A key part of the serverless drivers that have been supported now since their initial release is the query engine. The query engine is written to allow client queries to be reliably and efficiently converted into statements and then executed through the . |
