David Benchi

Integration Engineer at @Stripe

I love all the #Javascript family: @reactjs @angular @typescript @nodejs

[Cory House @housecor]

Problem: When you deploy a new version of your SPA, users with a tab open will keep using the old SPA code.

Yesterday, I shared one solution. People suggested dozens of useful variations and alternatives. 🙏

So, here are the best options in the massive thread.

6 ways to tell the SPA a new release is available, simplest options first:

1. Write the version from package.json into index.html as part of the build process. Poll index.html every x minutes and compare the server's index.html to the client's index.html.

2. Create an endpoint on the UI web server that reads the package.json version, and returns it. Poll this every x minutes. This is more efficient than option 1, because the payload is smaller.

3. Use web sockets or server sent events to push a notification to the UI after a deploy instead. This is especially attractive if you’re already using these technologies.

4. Use a service worker to notify the user when the UI is stale. For example, Vite's PWA plugin supports this.

5. Use an API proxy like Cloudfront to fetch the version without involving the backend. More here: https://t.co/Esr4Q9tOqS

6. Specify the app version in each HTTP call from the UI via a x-app-version header (or whatever name you like). Validate the x-app-version header on the API server. If x-app-version doesn't match the server's version, notify the UI in the response, either via an HTTP 205, 400, or 422 (the HTTP response you return depends on whether you want calls from a “stale” UI to succeed).

[David Benchi @david_benchi]

@totostache @Lukewh @LinkedIn Hmm

[David Benchi @david_benchi]

@Lukewh @totostache @LinkedIn Hmm

[Gergely Orosz @GergelyOrosz]

Another thing angering employees:

More new hires are joining the coming days/weeks. Klarna is reaching out to confirm to these new joiners that they are safe to join.

Rescinding offers: not cool. Klarna employees feel laying off tenured folks instead is worse though.

[David Benchi @david_benchi]

Rapid Event Notification System at Netflix by Netflix Technology Blog https://t.co/EjDXGzuPOP

[David Benchi @david_benchi]

Microservices Database Management Patterns and Principles by @ezozkme https://t.co/1zR4MFv5gp

[David Benchi @david_benchi]

I just read "Mac Setup for Web Development [2022]" by @rwieruch https://t.co/purLkmSsWX

[David Benchi @david_benchi]

Patterns to know before migrating your monolith to microservices by @abhi_kapoor6 in @gitconnected https://t.co/5Yyn0LH6at

[David Benchi @david_benchi]

"Git Cheat Sheet 📄 (50 commands + Free PDF and poster)" by @DoableDanny #DEVCommunity https://t.co/QFIOkovOj4

[David Benchi @david_benchi]

Interface vs Type alias in TypeScript 2.7 by @martin_hotell https://t.co/VsVhBZLZvQ

[David Benchi @david_benchi]

A must read article on #web3
@moxie >> Blog >> My first impressions of #web3 https://t.co/C2N3mfV9wh via @moxie

[David Benchi @david_benchi]

10 Must-Have React Developer Tools To Write Clean Code https://t.co/vTll6AI9pe via @DZoneInc

[David Benchi @david_benchi]

Prettier begins paying maintainers https://t.co/SGgNnGtGKu

[David Benchi @david_benchi]

Amazon’s Sr. Software Engineer at 27 — 8 important lessons I’ve learned so far in my career by Daniel Costa in @gitconnected https://t.co/yCxm1qlInh

[David Benchi @david_benchi]

It depends a lot on the business case you are facing to know if it will be worth using Micro-frontend architecture or not.
Business... Business... Business

https://t.co/5Iz1j1tY98

[David Benchi @david_benchi]

"Advanced JavaScript Series - Part 2: Execution Context and Call Stack" by @Pranav046 #DEVCommunity https://t.co/AFamqgTEi7

[David Benchi @david_benchi]

"Advanced JavaScript Series - Part 1: Behind the scenes (JavaScript Engine, ATS, Hidden Classes, Garbage Collection)" by @Pranav046 #DEVCommunity https://t.co/LXoWcaBw4I

[David Benchi @david_benchi]

How JavaScript Works behind the scenes? by @fixslyr https://t.co/W6WNcELSia

[David Benchi @david_benchi]

Refactoring Legacy Code with the Strangler Fig Pattern https://t.co/Fhgx1QE8uJ via @Shopify