Skip to content
Hallway
0:00 / 0:00

#dart#flutter#redis

Full-stack Dart with Simon Lightfoot: Pt 2 (The Boring Flutter Development Show, Ep. 60)

Flutter

634K subscribers • 172 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Simon Lightfoot
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Intermediate. Assumes working knowledge.

13K views4 years ago2 recommendations

Programming languagesCloud and DevOpsFull-stack frameworksDocker and containersGoogle Cloud

Simon Lightfoot and Craig Labenz build a full-stack Dart application using Redis and deploy it to Google Cloud Run.

In this episode, Simon Lightfoot and Craig Labenz continue their adventure with full-stack Dart. Building off their work in Episode 59, they venture deeper in Docker, Google Cloud Run, and HOPEFULLY reach the finish line. Chapters: - Introduction and recap - Storing the counter on the server - Sending data to all clients - Introducing Redis - Adding Redis - Adding PubSub from Redis - Using Redis for fanout - Deploying to Cloud Run Resources: Get started with Flutter → flutter.dev Simon Lightfoot on Twitter → goo.gle/3O9qb3Y Watch more episodes of the Boring Show here → goo.gle/BoringFlutterShow Subscribe to the Flutter channel → goo.gle/FlutterYT #Flutter #BoringShow #Developer

Why it's here

2 people recommend this

What people say. Recommended as an example of building full-stack Dart applications and handling state synchronization across multiple instances using Redis.

u/Pixelredditin r/FlutterDev • Recommends

Full-stack Dart with Simon Lightfoot: Pt 2 (The Boring Flutter Developme...
19View on Reddit

u/mtwichelin r/FlutterDev • Recommends

On “🥞 Dart Frog full stack tutorial”

Probably worth mentioning that, while Cloud Run is amazing, this example could run into problems if deployed there. Because Cloud Run automatically creates new instances with their own RAM, each instance would have its own count, so devices could get out of sync. A simple solution to this is use a cache like Memstore or Redis to store the count outside of the instances themselves. The Flutter boring show did something similar a while back you could draw inspiration from link to this video I totally get why this wasn’t included in this demo as it’d be way too complicated, but also good to know one of the trade offs with serverless haha
2View on Reddit