A streamlined approach to supporting data

Mitu892

Solutions as data complexity increases. -driven application development avoids unnecessary complexity while retaining depth and detail. Fitting perfectly with this philosophy became a key tool in our data journey. It’s time to get started. We’re super excited and can’t wait to see what you’ll build with it. Please share your thoughts as you delve deeper. Engage with us on Let’s build amazing data-driven applications together. Announcement Data Platform Don’t miss the next post. Support for serverless database drivers is now available in preview. 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 prob photo editing servies lems in a serverless environment. 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 accompanying database driver. The system used to work fine but a few months ago we noticed a trend of new database providers offering serverless database drivers written in . These drivers communicated with special endpoints. Our team knew that building a Java-based implementation that communicated with these new endpoints would be a daunting task. Diagram showing the client using the query engine to open a long-lived connection to the database. The client can communicate with the database without a driver adapter. Additionally, while it works with many database engines and providers, it can only connect to these databases through direct connections or through connection pooling.