Really happy with how our 100% @cloudflare Workers rendered ecom site is performing since launch a few weeks ago (home.bargains). There's no headless system in the backend. Just workers (and a tiny bit of DynamoDB). A bit about how we did it... (1/4)
@hichaelmart@LambrosPetrou@Cloudflare Interesting, but don't think of great use for us. >98% of our traffic hits LHR or MAN colo - Our DDB is in AWS eu-west-2 region. Less than 4% of our Workers requests pull data from AWS/DDB. Will look into it tho
@mike__builds@Cloudflare Sadly not. Product page ‘other product’ recommendations etc are from KV, everything you see on a category page inc filtering and sort is just Workers & KV, but search is too complex. Maybe one day with something like D1?
@drak2@Cloudflare@algolia That was my guess.. was hoping you had found a neat trick for KV. Algolia costs are insane, but doesn’t seem to be any other really solid options at the moment
@30thnight@Cloudflare We’ve built a stand alone content system for product and site data. When content is updated, events are sent from that system and end up in KV, time for updates to be reflected globally is 1-30 seconds (KV global replication time). Stripe just used for tokenised cards & payments
@drak2@Cloudflare This is fantastic.
How does your content team manage updates? Do they lean directly on Stripe & using product webhooks to populate CF KV?
@mike__builds@Cloudflare It’s @algolia all in the browser. The way their search works would never go via a Worker. Obviously their cost dwarfs everything else
@bernsno@Cloudflare Lower TCO, it seemed like a fun thing to do, it scales better especially for volatile traffic patterns, our destiny is now in our own hands rather than being stuck with design patterns decided by someone else. Wasn’t a walk in the park, but the right think for us
@LambrosPetrou@Cloudflare 100% of our customers are in the UK, so no point in global tables for us. Which is disappointing, as don’t get to flex the global nature of Workers. Dynamo is obv the slowest part of the stack, but such a tiny part of the whole system that it’s no big issue for us
Currently built using the Flareact framework, which we've been maintaining, but will move to NextJS on Cloudflare Pages when that's stable enough. It's nice to run a website with 0 servers and 0 relational DBs (3/4)