4 ms·
Ask HN: Do you use service workers for your web app?
I'm just curious to understand if anyone is using service workers for their web app in production and if so, what use cases does it solve particularly well.
More specifically, in terms of caching, apart from working offline how is it different from browser/CDN cache? What if your service worker itself is cached for sometime and you want to rollout an update? What are the best practices? How has your experience been maintaining service worker on a production app? What about security?
I know notifications can be done, server push with HTTP/2 etc. But which kind of web apps can make the best use of service workers and which ones shouldn't implement it?
- Jack000 9y agoI use service workers on http://svgnest.com http://svgnest.com no idea about caching, I mainly use it max out all the cores for the cpu bound algo. its probably good for browser based cryptocurrency mining too.
- detaro 9y agoThat sounds more like web workers than service workers? (web worker: get "background threads" for computation, service worker: intercept requests, get custom caching strategies, ...)
- Jack000 9y agooh oops I guess mixed up the terms. I hope these apis stick around because they seem kind of niche and under-utilized right now.
- maxharry 9y agoWe are Writers in UK we Provide you the Best Essay Writing Articles in UK check over here https://ukessay.com/assignments https://ukessay.com/assignments
- neilsimp1 9y agoI'm currently writing a PWA and using https://www.npmjs.com/package/sw-precache-webpack-plugin https://www.npmjs.com/package/sw-precache-webpack-plugin to generate the service worker on each build. It's nice because it's a whole chunk of what would otherwise be application logic that I now give zero thought too.