Why force your users to settle for either loading skeletons or slow page renders? Remix can bring your application rendering to the edge, but what about your data? Why should every request have to call back to a single database cluster in Virginia? For the best performance and experience for your users, store your data on the edge, alongside the rest of your application. We'll discuss how the original colocated server and database configuration worked, how it evolved with Jamstack, improved with next-gen data services, and how today's technology supports a new architecture altogether. But distributed systems are notoriously hard to design for, and edge-based storage is no different, with the challenges of synchronicity being a particularly difficult problem. I'll highlight the benefits of edge-based storage, how it compares to the other options, and I'll showcase a truly global Remix application built with Cloudflare's KV, Durable Objects and R2. Speaker bio: Greg is a Systems Engineer at Cloudflare working on Cloudflare Pages in the Emerging Technologies and Incubation department. Cloudflare Pages is a full-stack developer platform and they were very excited to add support for Remix at the end of last year. Before Pages, Greg worked with Cloudflare's Speed Team where he learned to appreciate the Network tab of DevTools. Greg has also contributed to the Web Almanac and numerous open-source projects, and, most importantly, he has his fingers crossed for enough snow to go skiing after Remix Conf! â›· Learn more at https://remix.run/conf/2022/speakers/greg-brimble
This video shows how to configure VS Code to debug your Remix loaders and actions. NOTE: You can now use the `debugger` statement instead of the external `debug()` function. I tried this before, but it didn't work. Not sure why it works now. You still can't set a breakpoint inside a route module, but you can add `debugger` statement and it will break there. You can then step through your code. I will be re-recording this video with this new info. Get the launch configuration here: https://rmx.fyi/debug
Have you heard about our new Remix Stacks template the K-pop Stack? It combines Remix, Supabase, Tailwind, and more to give you a note creation app with auth to help jump start your own Remix creation. Check out how to make it your own and get it deployed to fast and free! Repo: https://github.com/netlify-templates/kpop-stack Blog Post: https://www.netlify.com/blog/deploy-your-remix-supabase-app-today!/
HTTP Caching is a web fundamental every web developer should eventually learn. The quickest way to a slow website is to not understand caching and ofc, the best way to make your website fast is to take advantage of it. In this video we'll explain the basics of HTTP caching, how web browsers respond to it, and how CDNs take advantage of it, by building a bare-bones Node.js server and then quickly see how to specify caching headers in a Remix App.
In Today's episode will cover: - @Stripe Integration - Webhook Setup - Checkout Session and Payment Testing These videos are free and created for the community, support will be much appreciated! 🫶
Learn more at https://remix.run
Check out the new v2_dev docs 👉 https://remix.run/docs/en/main/other-api/dev-v2 Indie stack 👉 https://github.com/remix-run/indie-stack