🇫🇷 DevFest Nantes 2023

Slide 1

Slide 1 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! • THE 19TH OF OCTOBER, 2023. Bonjour, Nantes 👋 🇫🇷

Slide 2

Slide 2 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 🤯 MATHEUS ALBUQUERQUE • @ythecombinator

Slide 3

Slide 3 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 🤯 MATHEUS ALBUQUERQUE • @ythecombinator LET’S DISCUSS MORE AFTER!

Slide 4

Slide 4 text

This talk presents… ↝ The Past & The Future ↝ Islands Architecture ↝ Resumability ↝ Streaming SSR + Selective Hydration ↝ React Server Components ↝ Closing Thoughts

Slide 5

Slide 5 text

#question 🤔 Who of you are working with front- end? React? Angular? Vue?

Slide 6

Slide 6 text

#question 🤔 How and where do I want to render content?

Slide 7

Slide 7 text

HOW AND WHERE DO I WANT TO RENDER CONTENT? web server build server the client the Edge

Slide 8

Slide 8 text

HOW AND WHERE DO I WANT TO RENDER CONTENT? web server build server the client the Edge all at once partially progressively

Slide 9

Slide 9 text

HOW AND WHERE DO I WANT TO RENDER CONTENT? web server build server the client the Edge all at once partially progressively Where do you navigate? What is executed on load? When is data fetched? What do you bundle/serialize?

Slide 10

Slide 10 text

WHEN DOES AN APP BECOME INTERACTIVE?

Slide 11

Slide 11 text

WHEN DOES AN APP BECOME INTERACTIVE?

Slide 12

Slide 12 text

#question 🤔 How did we get here?

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

The Past HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

#research 📚 In the past 10 years, the median size for a desktop webpage has gone from 468 KB to 2284 KB, a 388.3% increase. — Web Almanac By HTTP Archive, 2021

Slide 18

Slide 18 text

#research 📚 For mobile, this jump is even more staggering — 145 KB to 2010 KB — a whopping 1288.1% increase. — Web Almanac By HTTP Archive, 2021

Slide 19

Slide 19 text

1995

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

↝ LANGUAGES LIKE PERL AND PHP ALLOWED DEVELOPERS TO RENDER BACKEND DATA SOURCES INTO HTML ↝ DEVELOPERS WERE NOW ABLE TO BUILD DYNAMIC SITES AND SERVE REAL-TIME DATA, OR DATA FROM A DATABASE TO AN END USER CGI SCRIPTING LANGUAGES

Slide 22

Slide 22 text

↝ THESE WORKED ON THE SERVER BECAUSE SERVERS WERE THE POWERFUL PART OF THE NETWORK ↝ THE BROWSER'S JOB WAS LIMITED: INTERPRETING THE DOCUMENT AND SHOWING THE PAGE ↝ THIS SOLUTION WAS ALL ABOUT SHOWING INFORMATION, NOT INTERACTING WITH IT CGI SCRIPTING LANGUAGES

Slide 23

Slide 23 text

#eureka 💡 JavaScript and browsers got powerful = we could do a ton of fun things directly on the client.

Slide 24

Slide 24 text

↝ YOU DON’T HAVE TO GO BACK TO THE SERVER FOR MORE REQUESTS ↝ YOU CAN CACHE THE CORE HTML AND JS BUNDLES ON A CDN ↝ AS THE WEB GOT MORE INTERACTIVE, CSR AND SPAS BECAME DEFAULT CLIENT-SIDE RENDERING (CSR)

Slide 25

Slide 25 text

#gotcha 🥸 We now had to be mindful of how our apps would render on a phone on a bus in the city center. — THE FUTURE (AND THE PAST) OF THE WEB IS SERVER SIDE RENDERING, BY ANDY JIANG

Slide 26

Slide 26 text

#eureka 💡 We now had to be mindful of how our apps would render on a phone on a bus in the city center. Back to the server! 🏃

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

↝ HTML IS READY TO BE DISPLAYED WHEN THE PAGE IS LOADED = HIGHER PERFORMANCE ↝ HTML IS NOT DEPENDENT ON THE END BROWSER = HIGHER COMPATIBILITY ↝ FOR INTERACTIVE WEBSITES, WE STILL NEED TO SEND JS (HYDRATION) SERVER-SIDE RENDERING (SSR)

Slide 30

Slide 30 text

🚨 INTERMISSION: Hydration HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 31

Slide 31 text

#definition 🧐 Hydration is the process of attaching behavior to declarative content to make it interactive. — WHY PROGRESSIVE HYDRATION IS HARDER THAN YOU THINK, BY MIŠKO HEVERY

Slide 32

Slide 32 text

↝ ASSOCIATE DOM ELEMENTS WITH THEIR CORRESPONDING EVENT HANDLERS ↝ ONCE A USER EVENT TRIGGERS A HANDLER, WE NEED TO UPDATE THE APP STATE ↝ ONCE THE APP STATE UPDATES, THE FRAMEWORK NEEDS TO RECREATE THE COMPONENT HIERARCHY HYDRATION: CHALLENGES 🤯

Slide 33

Slide 33 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 34

Slide 34 text

↝ DO WE SEND ALL JS ON EVERY REQUEST? OR DO WE BASE IT ON THE ROUTE? ↝ IS HYDRATION DONE TOP-DOWN? AND HOW EXPENSIVE IS THAT? ↝ HOW DOES THE DEVELOPER ORGANIZE THE CODE BASE? HYDRATION: QUESTIONS 🤯

Slide 35

Slide 35 text

HYDRATION: ISSUES INITIAL REQUEST HTML ARRIVES VIEW PAINTED JAVASCRIPT ARRIVES JAVASCRIPT IS PARSED — RESUMABILITY, WTF?, BY RYAN CARNIATO 0 100

Slide 36

Slide 36 text

GET HTML DOWNLOAD JS PARSE + EXECUTE JS RECOVER STATE + BIND LISTENERS 🟢 FAST (USUALLY) HYDRATION: ISSUES

Slide 37

Slide 37 text

GET HTML DOWNLOAD JS PARSE + EXECUTE JS RECOVER STATE + BIND LISTENERS 🔴 SLOW (ON BAD NETWORK CONDITIONS) HYDRATION: ISSUES

Slide 38

Slide 38 text

GET HTML DOWNLOAD JS PARSE + EXECUTE JS RECOVER STATE + BIND LISTENERS 🔴 SLOW (DEPENDING ON THE DEVICE AND AMOUNT OF JAVASCRIPT) HYDRATION: ISSUES

Slide 39

Slide 39 text

GET HTML DOWNLOAD JS PARSE + EXECUTE JS RECOVER STATE + BIND LISTENERS 🔴 SLOW (DEPENDING ON THE AMOUNT OF DOM NODES TO BE TRAVERSED AND REFERENCES TO BE RE-BOUND TO LISTENERS) HYDRATION: ISSUES

Slide 40

Slide 40 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 41

Slide 41 text

Islands Architecture HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2021 2022 2020

Slide 42

Slide 42 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 43

Slide 43 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

#definition 🧐 Islands are a component-based architecture that suggests a compartmentalized view of the page with static and dynamic islands. — ISLANDS ARCHITECTURE, BY PATTERNS.DEV

Slide 46

Slide 46 text

↝ SELECTIVELY, PROGRESSIVELY ENHANCING BITS OF SERVER-RENDERED HTML WITH CLIENT-SIDE JS ↝ SMALL, FOCUSED, CHUNKS OF INTERACTIVITY WITHIN SERVER-RENDERED WEB PAGES ↝ SINGLE APPLICATION IN CONTROL OF FULL-PAGE RENDERING → MULTIPLE ENTRY POINTS ISLANDS ARCHITECTURE

Slide 47

Slide 47 text

↝ THE SCRIPT FOR THE ISLANDS CAN BE DELIVERED AND HYDRATED INDEPENDENTLY, ALLOWING THE REST OF THE PAGE TO BE JUST STATIC HTML ↝ THE OUTPUT OF ISLANDS IS PROGRESSIVELY ENHANCED HTML ↝ MORE SPECIFICITY AROUND HOW THE ENHANCEMENT OCCURS ISLANDS ARCHITECTURE

Slide 48

Slide 48 text

ISLANDS ARCHITECTURE PAGE LAYOUT POST TITLE POST CONTENT COMMENTS SOCIAL CTA

Slide 49

Slide 49 text

ISLANDS ARCHITECTURE PAGE LAYOUT (SSR’D) POST TITLE (SSR'D) POST CONTENT (SSR’D) COMMENTS PLACEHOLDER (SSR) SOCIAL CTA PLACEHOLDER (SSR) COMMENTS “APP” (SSR’D + HYDRATION SCRIPT) SOCIAL CTA “APP” (SSR’D + HYDRATION SCRIPT)

Slide 50

Slide 50 text

ISLANDS ARCHITECTURE PAGE LAYOUT (SSR’D) POST TITLE (SSR'D) POST CONTENT (SSR’D) COMMENTS PLACEHOLDER (SSR’D) SOCIAL CTA PLACEHOLDER (SSR’D) COMMENTS “APP” (SSR’D + HYDRATION SCRIPT) SOCIAL CTA “APP” (SSR’D + HYDRATION SCRIPT)

Slide 51

Slide 51 text

↝ STANDALONE: Astro, Iles, Qwik, Marko, Nano JSX, Capri ↝ PREACT: Fresh, preact-island, microsite ↝ SOLIDJS: Solid Start, isolid ↝ SVELTE: Elder.js ISLANDS ARCHITECTURE

Slide 52

Slide 52 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 53

Slide 53 text

↝ STREAMING RENDERING + AUTOMATIC PARTIAL HYDRATION + COMPILER ↝ AUTOMATIC PARTIAL HYDRATION ALLOWS INTERACTIVE COMPONENTS TO HYDRATE THEMSELVES ↝ HYDRATION CODE IS ONLY SHIPPED FOR INTERACTIVE COMPONENTS ISLANDS ARCHITECTURE (WITH MARKO) 🤯

Slide 54

Slide 54 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 55

Slide 55 text

↝ BY DEFAULT, SHIPS ZERO JAVASCRIPT ↝ EVERY ISLAND IS LOADED IN PARALLEL ↝ MULTI-FRAMEWORK: BUILD ISLANDS WITH REACT, PREACT, SVELTE, VUE, AND OTHERS ↝ YOU CAN SPECIFY THE LOADING STRATEGY FOR EACH ISLAND INDIVIDUALLY ISLANDS ARCHITECTURE (WITH ASTRO)

Slide 56

Slide 56 text

- - - import MyReactComponent from ' . . /components/MyReactComponent.jsx'; - - - ISLANDS ARCHITECTURE (WITH ASTRO)

Slide 57

Slide 57 text

- - - import MyReactComponent from ' . . /components/MyReactComponent.jsx'; - - - ISLANDS ARCHITECTURE (WITH ASTRO)

Slide 58

Slide 58 text

#case💡 An e-commerce. Product pages have static descriptions and links. Interactive components (e.g., image carousels, search bar) are available in different regions.

Slide 59

Slide 59 text

#case💡 An internet banking app. The account details page contains a list of static transactions with filters providing some interactivity.

Slide 60

Slide 60 text

🟢 REDUCES THE AMOUNT OF JAVASCRIPT CODE SHIPPED TO THE CLIENT 🟢 FASTER PAGE LOADS AND TIME TO INTERACTIVE (TTI) 🟢 KEY CONTENT IS AVAILABLE ALMOST IMMEDIATELY TO THE USER 🟢 STATIC CONTENT IS RENDERED ON THE SERVER = PAGES ARE SEO-FRIENDLY GREAT 🟡 HIGHLY INTERACTIVE PAGES WOULD PROBABLY REQUIRE THOUSANDS OF ISLANDS NOT GREAT ISLANDS ARCHITECTURE

Slide 61

Slide 61 text

Slide 62

Slide 62 text

Resumability HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2020 2021 2022

Slide 63

Slide 63 text

#hotTake 🌶 A considerable part of the modern isomorphic landscape is built on the back of libraries that weren't initially created for server rendering.

Slide 64

Slide 64 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 65

Slide 65 text

#question 🤔 What if frameworks were built on SSR in the first place?

Slide 66

Slide 66 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 67

Slide 67 text

OPA LANGUAGE 🤯

Slide 68

Slide 68 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

#definition 📖 Resumability is about pausing execution in the server and resuming execution in the client without having to replay and download all of the application logic. — RESUMABLE VS. HYDRATION, QWIK

Slide 71

Slide 71 text

↝ SOME WORK → PAUSE → RESUME ↝ USE WHAT HAPPENED DURING THE EXECUTION ON THE SERVER AND AVOID EXTRA WORK WHEN THE APPLICATION STARTS IN THE BROWSER ↝ ATTACHES GLOBAL EVENT HANDLERS AT STARTUP AND THEN ONLY RUNS THE NECESSARY CODE ON INTERACTION RESUMABILITY

Slide 72

Slide 72 text

↝ EVENT HANDLER CREATION HAPPENS BEFORE THE EVENT IS TRIGGERED (EAGER) ↝ ALL POSSIBLE EVENT HANDLERS ARE CREATED AND REGISTERED (SPECULATIVE) ↝ CLIENT REDOES WORK ↝ REQUIRES THE FRAMEWORK TO DOWNLOAD AND EXECUTE THE COMPONENTS TO FIGURE OUT HIERARCHY HYDRATION ↝ EVENT HANDLER CREATION HAPPENS AFTER THE EVENT IS TRIGGERED (LAZY) ↝ ONLY TRIGGERED EVENTS ARE CREATED AND REGISTERED (AS-NEEDED) ↝ CLIENT DOESN'T REDO WORK (VIA DESERIALIZATION) ↝ REQUIRES ALL THE INFORMATION TO BE SERIALIZED IN THE HTML RESUMABILITY HYDRATION VS. RESUMABILITY

Slide 73

Slide 73 text

Slide 74

Slide 74 text

RESUMABILITY: SERIALIZATION { "handlers": [ … ], "state": { … }, "hierarchy": { … }, } DISPLAY HTML RESUME STATE (JSON PARSE) 🟢 INTERACTIVE

Slide 75

Slide 75 text

RESUMABILITY: SERIALIZATION { "handlers": [ … ], "state": { … }, "hierarchy": { … }, } DISPLAY HTML RESUME STATE (JSON PARSE) 🟢 INTERACTIVE

Slide 76

Slide 76 text

RESUMABILITY: SERIALIZATION { "handlers": [ … ], "state": { … }, "hierarchy": { … }, } DISPLAY HTML RESUME STATE (JSON PARSE) 🟢 INTERACTIVE

Slide 77

Slide 77 text

Slide 78

Slide 78 text

↝ CLIENT REDOES WORK ↝ ISLAND-LEVEL ISLANDS ↝ CLIENT DOESN'T REDO WORK ↝ SUB-COMPONENT LEVEL (SMALLER) RESUMABILITY HYDRATION VS. RESUMABILITY 🤯

Slide 79

Slide 79 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 80

Slide 80 text

🟢 STARTUP PERFORMANCE 🟢 RENDERING PERFORMANCE (ONLY CHANGED COMPONENTS NEED TO BE RE-RENDERED) 🟢 FINE-GRAINED LAZY-LOADING 🟢 PROGRESSIVE INTERACTIVITY GREAT 🟡 *PRELOAD CRITICAL PAGE INTERACTIONS 🟡 THE ONLY OPTION FOR DEVELOPERS TO LEVERAGE RESUMABILITY IS TO USE QWIK 🟡 TOO LITTLE DISCUSSION AVAILABLE ON THE IDEA NOT GREAT RESUMABILITY

Slide 81

Slide 81 text

Slide 82

Slide 82 text

#hotTake 🌶 Qwik is an example of the outside of the box thinking that is sometimes required on the web.

Slide 83

Slide 83 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2020 2021 2022 Incremental Static Generation

Slide 84

Slide 84 text

↝ AN EVOLUTION OF THE JAMSTACK ↝ ADDRESSES SOME ISSUES OF SSR AND CSR ↝ UPDATE STATIC CONTENT WITHOUT A FULL REBUILD ↝ MADE POPULAR BY NEXT.JS INCREMENTAL STATIC GENERATION

Slide 85

Slide 85 text

INCREMENTAL STATIC GENERATION — A COMPLETE GUIDE TO INCREMENTAL STATIC REGENERATION (ISR) WITH NEXT.JS BY LEE ROBINSON

Slide 86

Slide 86 text

/ / pages/talks/[id].js export async function getStaticProps({ params }) { return { props: { talk: await getTalk(params.id) }, revalidate: 60 } } INCREMENTAL STATIC GENERATION (WITH NEXT.JS)

Slide 87

Slide 87 text

/ / pages/talks/[id].js export async function getStaticProps({ params }) { return { props: { talk: await getTalk(params.id) }, revalidate: 60 } } INCREMENTAL STATIC GENERATION (WITH NEXT.JS)

Slide 88

Slide 88 text

INCREMENTAL STATIC GENERATION GENERATE PAGE 0 SECS FROM CACHE

Slide 89

Slide 89 text

INCREMENTAL STATIC GENERATION GENERATE PAGE 0 SECS FROM CACHE

Slide 90

Slide 90 text

INCREMENTAL STATIC GENERATION GENERATE PAGE 0 SECS FROM CACHE GENERATE PAGE UPDATE CACHE 60 SECS

Slide 91

Slide 91 text

INCREMENTAL STATIC GENERATION GENERATE PAGE 0 SECS FROM CACHE 60 SECS STALE PAGE FROM CACHE

Slide 92

Slide 92 text

#case💡 A growing blog. A new post shouldn't require a rebuild for all the existing pages. You don't want to rebuild and redeploy the site just because of a typo in one of the posts either.

Slide 93

Slide 93 text

#case💡 A huge e-commerce. Is it possible to statically generate millions of products with every deployment? Even at 1 page/ms, it would still take hours to rebuild the entire site.

Slide 94

Slide 94 text

🟢 EVERYTHING FROM STATIC GENERATION 🟢 DYNAMIC CONTENT GREAT 🟡 SERVER COSTS NOT GREAT INCREMENTAL STATIC GENERATION

Slide 95

Slide 95 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 96

Slide 96 text

🟢 EVERYTHING FROM STATIC GENERATION 🟢 DYNAMIC CONTENT GREAT (ON DEMAND) INCREMENTAL STATIC GENERATION NOT GREAT

Slide 97

Slide 97 text

Streaming SSR + Selective Hydration HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2020 2021 2022

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 101

Slide 101 text

HYDRATION IN REACT: THE BAD PARTS™ ↝ HYDRATION COULD ONLY BEGIN AFTER THE ENTIRE DATA WAS FETCHED AND RENDERED ↝ USERS COULDN’T INTERACT WITH THE PAGE UNTIL HYDRATION WAS COMPLETE FOR THE WHOLE PAGE ↝ PARTS OF YOUR APP THAT LOAD FAST WOULD ALWAYS HAVE TO WAIT FOR THE SLOW ONES

Slide 102

Slide 102 text

FETCHING DATA (SERVER) RENDERING HTML (SERVER) LOADING CODE (CLIENT) HYDRATING TIME TO FIRST BYTE FIRST CONTENTFUL PAINT TIME TO INTERACTIVE HYDRATION IN REACT: THE BAD PARTS™

Slide 103

Slide 103 text

TIME TO FIRST BYTE FIRST CONTENTFUL PAINT TIME TO INTERACTIVE […] FETCHING DATA (SERVER) RENDERING HTML (SERVER) HYDRATING LOADING CODE (CLIENT) […] […] […] […] […] […] (STREAMING SSR +) SELECTIVE HYDRATION

Slide 104

Slide 104 text

↝ pipeToNodeStream + createRoot + ↝ REACT PRIORITIZES HYDRATING THE PARTS THAT THE USER INTERACTED WITH BEFORE THE REST ↝ COMPONENTS CAN BECOME INTERACTIVE FASTER BY ALLOWING THE BROWSER TO DO OTHER WORK AT THE SAME TIME AS HYDRATION (STREAMING SSR +) SELECTIVE HYDRATION

Slide 105

Slide 105 text

↝ REACT WON'T WAIT FOR HUGE COMPONENTS TO LOAD TO CONTINUE STREAMING HTML FOR THE REST OF THE PAGE ↝ WHEN THE HTML BECOMES AVAILABLE ON THE SERVER, IT WILL BE ADDED TO THE SAME STREAM ALONG WITH A SCRIPT TAG AND INSERTED IN THE RIGHT PLACE (STREAMING SSR +) SELECTIVE HYDRATION

Slide 106

Slide 106 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 107

Slide 107 text

React Server Components HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2020 2021 2022

Slide 108

Slide 108 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

No content

Slide 112

Slide 112 text

↝ AHEAD-OF-TIME REACT RENDERING (DURING THE BUILD OR ON THE SERVER) ↝ A ROUTING PARADIGM INTEGRATED WITH DATA FETCHING AND BUNDLING ↝ UNRELATED TO SSR/HYDRATION REACT SERVER COMPONENTS

Slide 113

Slide 113 text

↝ ALMOST IDENTICAL TO HOW ISLANDS WORK ↝ “use client” MARKS A BOUNDARY BETWEEN TWO MODULE GRAPHS ↝ EACH COMPONENT DECIDES WHETHER TO BE A SERVER COMPONENT OR TO STICK WITH BEING A SERVER + CLIENT COMPONENT REACT SERVER COMPONENTS

Slide 114

Slide 114 text

↝ THE CODE FOR SERVER COMPONENTS IS NEVER DELIVERED TO THE CLIENT ↝ ACCESS TO THE BACK-END FROM THE TREE ↝ MAY BE REFETCHED WHILE MAINTAINING CLIENT- SIDE STATE INSIDE OF THE TREE REACT SERVER COMPONENTS

Slide 115

Slide 115 text

REACT SERVER COMPONENTS: BEFORE — RSC FROM SCRATCH. PART 1: SERVER COMPONENTS #5 BY DAN ABRAMOV

Slide 116

Slide 116 text

REACT SERVER COMPONENTS: AFTER — RSC FROM SCRATCH. PART 1: SERVER COMPONENTS #5 BY DAN ABRAMOV

Slide 117

Slide 117 text

🟡 A LOT OF DATA TO SEND ALONG THE WIRE EVERY SERVER RE-RENDER 🟡 MUCH MORE ORCHESTRATION NEEDED 🟡 STILL EXPERIMENTAL 🟡 ONLY FEW OPTIONS FOR DEVELOPERS TO LEVERAGE RSC NOT GREAT REACT SERVER COMPONENTS 🟢 THE CODE FOR SERVER COMPONENTS IS NEVER DELIVERED TO THE CLIENT 🟢 ACCESS TO THE BACK-END FROM THE TREE 🟢 MAY BE REFETCHED WHILE MAINTAINING CLIENT-SIDE STATE INSIDE OF THE TREE GREAT

Slide 118

Slide 118 text

No content

Slide 119

Slide 119 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 120

Slide 120 text

< ! - - Database, file, and socket access from JavaScript - - > var resultSet = Jaxer.DB.execute("SELECT * FROM myTable"); var newPrice = resultSet.rows[0].price; < ! - - Directly call server-side functions from the browser - - > function getPriceFromServer() { return 42; } Price < ! - - Share validation code on the browser and server - - > function validateCreditCard(number) {} REACT SERVER COMPONENTS (PRIOR ART)

Slide 121

Slide 121 text

Slide 122

Slide 122 text

No content

Slide 123

Slide 123 text

No content

Slide 124

Slide 124 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 125

Slide 125 text

REACT SERVER COMPONENTS

Slide 126

Slide 126 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 127

Slide 127 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 128

Slide 128 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 129

Slide 129 text

The Edge HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! 1993 1998 2008 2017 2020 2021 2022

Slide 130

Slide 130 text

No content

Slide 131

Slide 131 text

#definition 🧐 Edge Functions allow you to serve content from the CDN server closest to the user. — UNDERSTANDING EDGE FUNCTIONS: THE EDGE AND BEYOND

Slide 132

Slide 132 text

THE EDGE: FUNCTIONS ↝ SERVERLESS FUNCTIONS ARE DEPLOYED TO A SPECIFIC REGION WHERE THEY RUN REGARDLESS OF THE INITIATOR’S ORIGIN. ↝ EDGE FUNCTIONS RUN AS CLOSE TO THE REQUESTOR AS THEY CAN (ON A DISTRIBUTED EDGE SERVER).

Slide 133

Slide 133 text

THE EDGE ↝ BRINGING COMPUTING CLOSER TO THE SOURCE OF THE DATA ↝ FEWER PROCESSES IN THE CLOUD ↝ MINIMIZES THE NEED FOR LONG DISTANCE COMMUNICATIONS BETWEEN CLIENT AND SERVER ↝ REDUCES LATENCY AND BANDWIDTH USAGE

Slide 134

Slide 134 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 135

Slide 135 text

THE EDGE Location Heroku TTFB Frankfurt 339.95ms Amsterdam 382.62ms London 338.09ms New York 47.55ms Dallas 144.64ms San Francisco 302ms Singapore 944.14ms Sydney 889.85ms Tokyo 672.49ms Bangalore 984.39ms — THE FUTURE OF THE WEB IS ON THE EDGE, BY ANDY JIANG

Slide 136

Slide 136 text

THE EDGE Location Heroku TTFB Deno TTFB Frankfurt 339.95ms 28.45ms Amsterdam 382.62ms 29.72ms London 338.09ms 22.3ms New York 47.55ms 41.29ms Dallas 144.64ms 29.28ms San Francisco 302ms 44.24ms Singapore 944.14ms 528.57ms Sydney 889.85ms 26.46ms Tokyo 672.49ms 19.04ms Bangalore 984.39ms 98.23ms — THE FUTURE OF THE WEB IS ON THE EDGE, BY ANDY JIANG

Slide 137

Slide 137 text

THE EDGE

Slide 138

Slide 138 text

HYDRATION STREAMING SSR ISLANDS RESUMABILITY SELECTIVE HYDRATION RSC CSR SSR STATIC RENDERING INCREMENTAL STATIC GENERATION PROGRESSIVE HYDRATION VIEW TRANSITIONS EDGE RENDERING SPA MPA PARTIAL HYDRATION

Slide 139

Slide 139 text

Slide 140

Slide 140 text

The Future 🔮 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 141

Slide 141 text

— ISLANDS & SERVER COMPONENTS & RESUMABILITY, OH MY!, BY RYAN CARNIATO

Slide 142

Slide 142 text

ROUTING (& MPAs vs. SPAs)

Slide 143

Slide 143 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 144

Slide 144 text

HYDRATION

Slide 145

Slide 145 text

OKB JAVASCRIPT

Slide 146

Slide 146 text

CODE EXTRACTION

Slide 147

Slide 147 text

CODE EXTRACTION

Slide 148

Slide 148 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 149

Slide 149 text

CODE EXTRACTION import json from "./foo.json" with { type: "json" }; / / 🤔 🤔 🤔 import ComponentA from "./A" with { type: "client" } import ComponentB from "./B" with { type: "both" }

Slide 150

Slide 150 text

(WHY) IS THE FUTURE

Slide 151

Slide 151 text

Closing Thoughts HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 152

Slide 152 text

THE SOLUTION TO THE PROBLEM ONLY CHANGES THE PROBLEM. #1 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 153

Slide 153 text

WHILE SEEN AS COMPETITIVE, A LOT OF THESE ARE ACTUALLY COMPLEMENTARY! — RYAN CARNIATO #2 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 154

Slide 154 text

🏝 REDUCE JAVASCRIPT FOOTPRINT BY EXPLICITLY DENOTING WHAT GOES TO THE CLIENT. 🏝 INCREDIBLY OPTIMAL AT SOLVING FOR CODE AND DATA SERIALIZATION SIZE. 🏝 ISLANDS ⚛ EXTENDS ISLANDS WITH CLIENT-SIDE ROUTING AND PROPER STATE PRESERVATION. ⚛ THE ONLY ISLAND-LIKE SOLUTION THAT PROPERLY ACCOUNTS FOR THE STATE WHILE CLIENT-NAVIGATING. ⚛ SERVER COMPONENTS ▶ INSTEAD OF REDUCING THE AMOUNT THAT IS HYDRATED, LOOKS TO REMOVE THE EXECUTION COST OF HYDRATION. ▶ THE ONLY APPROACH THAT REDUCES THE COST OF THE HYDRATION THAT REMAINS. ▶ RESUMABILITY — ISLANDS & SERVER COMPONENTS & RESUMABILITY, OH MY!, BY RYAN CARNIATO

Slide 155

Slide 155 text

Slide 156

Slide 156 text

Slide 157

Slide 157 text

THE SAME PATTERN CAN BE BENEFICIAL AND DETRIMENTAL IT IS ALSO QUITE LIKELY THAT DIFFERENT TYPES OF PAGES REQUIRE DIFFERENT RENDERING PATTERNS ON THE SAME WEBSITE. #3 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 158

Slide 158 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 159

Slide 159 text

No content

Slide 160

Slide 160 text

APPLICATION HOLOTYPES Portfolio Content Storefront Social Network I m m ersive Holotype Personal Blog CNN Amazon Facebook Figma Interactivity Minimal Linked Articles Purchase Multi-Point, Real-time Everything Session Depth Shallow Shallow Shallow - Medium Extended Deep Values Simplicity Discover-ability Load Performance Dynamicism I m m ersiveness Routing Server Server, HTML Swap HTML Swap, Hybrid Hybrid, Client Client Rendering Static Static, SSR Static, SSR SSR CSR Hydration None Progressive, Partial Partial, Resumable Any None (CSR) Frameworks 11ty Astro, Elder Marko, Qwik, Hydrogen Next, Remix Create React App — PATTERNS FOR BUILDING JAVASCRIPT WEBSITES IN 2022, BY RYAN CARNIATO

Slide 161

Slide 161 text

#4 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 162

Slide 162 text

IT'S EASY TO THINK WE'RE JUST GOING BACK TO RENDERING HTML ON THE SERVER BUT THESE DAYS THE BOUNDARIES ARE VERY DIFFERENT. #4 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 163

Slide 163 text

SOFTWARE DEVELOPMENT CONTINUALLY GOES THROUGH CYCLES. WHAT’S DIFFERENT NOW? WHAT’S TURNED INTO LOST ART? #5 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 164

Slide 164 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 165

Slide 165 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 166

Slide 166 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 167

Slide 167 text

No content

Slide 168

Slide 168 text

IT ALL SOUNDS INCREDIBLY COMPLEX! WE'RE ADDRESSING THE UNCERTAINTIES OF THE MODERN WEB WHEN IT COMES TO CONNECTION QUALITY AND CLIENT DEVICE COMPUTATIONAL CAPABILITY. #6 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 169

Slide 169 text

A PICTURE IS WORTH A THOUSAND WORDS. #7 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 170

Slide 170 text

THIS IS ME, NINE YEARS AGO, PRESENTING ABOUT IONIC AT AN IOS DEVELOPERS MEETUP TELLING THEM THAT ANGULAR WOULD BE THE FUTURE OF MOBILE DEVELOPMENT.

Slide 171

Slide 171 text

A PICTURE IS WORTH A THOUSAND WORDS. DON'T ALWAYS TRUST SPECULATIONS AND PREDICTIONS! #7 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 172

Slide 172 text

THERE'S NO SILVER BULLET. IDENTIFY YOUR CORE METRICS. ALWAYS TRY TO CORRELATE BUSINESS METRICS WITH PERFORMANCE. #8 HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY!

Slide 173

Slide 173 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! ↑ ALL THE LINKS! 🧑🏫 TECHLABS 🐦 @ythecombinator 👨💻 MEDALLIA ⚡ GDE

Slide 174

Slide 174 text

HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! ↑ FEEDBACK!

Slide 175

Slide 175 text

THAT’S ALL, FOLKS! MERCI! 👋 🇫🇷 QUESTIONS? ↑ ALL THE LINKS! HYDRATION, ISLANDS, STREAMING, RESUMABILITY… OH MY! MATHEUS ALBUQUERQUE • @ythecombinator