Load dynamic serverless content faster with search

Slide 1

Slide 1 text

Josh Dzielak Load Dynamic Serverless Content Faster with Search Developer Relations Lead, Algolia 8/10/2017 #AlgoliaSearchParty @dzello github.com/dzello

Slide 2

Slide 2 text

> No application server > Caching is easier > HTML can be pre-generated > Possible to serve through a CDN Static sites are fast!

Slide 3

Slide 3 text

- Migrated from WordPress to static site - Hosted on Netlify - Uses APIs including Algolia, Stripe and Cloudinary Smashing Magazine - 10x faster! Beta: https://next.smashingmagazine.com/ From 800ms to 80ms time to first load

Slide 4

Slide 4 text

Source: https://next.smashingmagazine.com/

Slide 5

Slide 5 text

> Some content can’t be pre-built e.g. user-generated or frequently updated > At runtime, this content must be fetched by the browser from: - A backend - An API > If this step takes too long, the site can still feel slow But not everything is static!

Slide 6

Slide 6 text

Source: https://blog.algolia.com/performant-web-animations/ “Developers often invest quite a bit of time to reduce first page loads by even a few milliseconds, but forget to consider the impact of the interactions that follow.” — Emily Hayman, Solutions Engineer, Algolia

Slide 7

Slide 7 text

> Very low-latency search endpoints; tiny payloads Ideal response time: ~10ms server, ~40ms end-to-end How can Algolia help?

Slide 8

Slide 8 text

> Global index replication; like a CDN for dynamic content How can Algolia help?

Slide 9

Slide 9 text

> Custom rank records in advance; no query needed, relevant results can be served immediately How can Algolia help?

Slide 10

Slide 10 text

Demo! Algolia vs. “Backend” https://algolia-content-load.glitch.me/

Slide 11

Slide 11 text

Josh Dzielak Thank you! Developer Relations Lead, Algolia 8/10/2017 #AlgoliaSearchParty @dzello github.com/dzello