1 of 32

Database Access on the Edge with Cloudflare Workers & Prisma

Prisma

www.prisma.io

2 of 32

Lorem ipsum dolor sit amet consectetur

Alex Ruheni

Developer Advocate at Prisma

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed egestas faucibus velit, sit amet vestibulum dolor interdum in.

@ruheni_alex

@ruheni

www.prisma.io

3 of 32

Agenda

01

Cloudflare Workers – The Edge ⚡️

02

Prisma – best DX with databases

03

Demo 👨🏾‍🏭

04

Conclusion

3

www.prisma.io

4 of 32

Lorem ipsum dolor sit amet consectetur

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed egestas faucibus velit, sit amet vestibulum dolor interdum in.

Cloudflare Workers/

The Edge ⚡️

www.prisma.io

5 of 32

Cloudflare Workers vs Traditional Serverless

www.prisma.io

6 of 32

The Good Parts

– Distributed

– Lightweight

– Higher performance

6

The Edge

www.prisma.io

As mentioned before, it’s distributed.

“Traditional serverless” functions are deployed to specific data centers.
In contrast, Cloudflare Workers runs your application code much closer to the user, possibly in the same city!

It’s lighter:

The platform is built on top of the V8 engine – the engine that powers Chromium-based browsers such as Chrome, and the Node.js runtime.
Whenever your CFW is invoked, instead of provisioning a container for your lambda function, CFW spins up a V8 isolate that is significantly smaller
If you have heard about the cold-start problem on severless , then you know why this is exciting!

Higher performance

Its execution environment is lighter, which leads to a shorter startup time or possibly even none.
You would also experience lower latency whenever you invoke your function because it would be invoked from the data center closest to you.

This all sounds delightful but CFW is still serverless and suffers from the some of the same problems “traditional” serverless does

NEXT SLIDE: The hard parts of working with CFW

7 of 32

Serverless Pains

– Long-lived TCP connections

– Different interfaces

– Managing connections

7

The Edge

www.prisma.io

Some of them include:

Connecting to databases is a challenge

The V8 engine supports sending only HTTP-based connections. However, most traditional databases use long-lived TCP connections. So that’s a bummer.

Different databases present different implementations of their interfaces of how you can connect to them

Database connections are stateful and serverless environments are stateless – you can easily run out of database connections because every worker creates a new connection pool

When this happens, requests will start failing.

So, how can you solve this?

You have a number of options available to you (just like the rest of the JS ecosystem - joke):

You can use one of CF’s solutions such as Workers KV (key-value), and Durable objects
If you have an existing database, you can use:

PostgreREST - Postgres-specific

web server that turns your PostgreSQL database into a RESTful API.

A modification of the Postgres and MySQL drivers
Prisma – via the Prisma Data Proxy. 🎉

NEXT SLIDE: Introduction to the Prisma Data Proxy

8 of 32

Prisma Data Proxy 🎉

The Solution

www.prisma.io

9 of 32

Lorem ipsum dolor sit amet consectetur

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed egestas faucibus velit, sit amet vestibulum dolor interdum in.

Next-generation ORM for Node.js and Typescript

Prisma

www.prisma.io

10 of 32

Core Benefits of Prisma

– Boost Productivity

– Increase Confidence

10

www.prisma.io

11 of 32

Prisma

11

www.prisma.io

12 of 32

Prisma Data Proxy

Get started for free today at cloud.prisma.io

12

www.prisma.io

13 of 32

Lorem ipsum dolor sit amet consectetur

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed egestas faucibus velit, sit amet vestibulum dolor interdum in.

Let’s build that thing! 💪🏾

Demo

www.prisma.io

14 of 32

Follow along

GitHub: github.com/ruheni/prisma-cloudflare-workers

Live Demo: prisma-cf-workers.ruheni.workers.dev

14

www.prisma.io

15 of 32

16 of 32

Recap

The Edge ⚡️
Prisma and the Prisma Data Proxy
The future of databases on the Edge with Prisma

16

www.prisma.io

17 of 32

Lorem ipsum dolor sit amet consectetur

Thank you!

Alex Ruheni,

Developer Advocate at Prisma

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed egestas faucibus velit, sit amet vestibulum dolor interdum in.

@ruheni_alex

@ruheni

www.prisma.io

18 of 32

Thinking in objects

Prisma Client’s intuitive query API always returns plain JS objects

19 of 32

Thinking in objects

Prisma Client’s intuitive query API always returns plain JS objects

20 of 32

Easy relations (1)

Nested queries instead of complex JOINs

21 of 32

Easy relations (2)

Nest queries arbitrarily deep

22 of 32

Easy relations (3)

Fluent API to traverse relationships (method chaining)

23 of 32

Auto-completing DB queries

Generated type definitions enable auto-completion for all DB queries

24 of 32

Designed for building APIs

Save boilerplate with dedicated queries for filters, pagination & sorting

25 of 32

Prisma Migrate

EASY DATABASE MIGRATIONS

26 of 32

Human-readable DB schema

Easy and intuitive data modelling

27 of 32

Single-source of truth

Keep database schema and application models in sync

Prisma schema

(models, enums, ...)

Database

Application models

maps to

generates

28 of 32

Modeling relations naturally

One-to-one relations

29 of 32

Modeling relations naturally

One-to-many relations

30 of 32

Modeling relations naturally

Many-to-many relations

31 of 32

Prisma Studio

MODERN DATABASE GUI

32 of 32

A visual interface for your DB

View and edit application data with the ease of a spreadsheet

Easy & intuitive
Filters, sorting & pagination
Natural relation traversal
Keyboard shortcuts
Based on Prisma models