News for hackers. Stuff that matters.

A comment on 35% Faster Than The Filesystem (2017). Parent comment

Re:35% Faster Than The Filesystem (2017) by falcolas on Sunday August 18, 2019 @10:16AM (#20730239)
Personal opinion: Those things (static assets) belong in a container with Nginx serving them (and that’s not even counting SAAS options like S3). Easy to integrate with CDNs, easy to update, easy to roll out and back. And you get to take advantage of layers to keep the network and disk usage minimal.
[ Parent | on HN ]
Re:35% Faster Than The Filesystem (2017) by zaroth on Sunday August 18, 2019 @10:52AM (#20730466)
I don’t see how a container solves the backing store / source of truth problem?

How are changes getting put into the container? Are you versioning the container each time a file is changed or added? When files change are all instances of the containers being restarted to get the new/changed files?

[ Parent | on HN ]
Re:35% Faster Than The Filesystem (2017) by markbnj on Sunday August 18, 2019 @12:40PM (#20731262)
One answer: the files are stored in git and the image is built on commit and tagged with the current ref, then pushed. The deployment is then updated to reference the new tag and services are restarted, pulling the new image and launching the new container. This is the typical ci/cd setup for kubernetes deployments.
[ Parent | on HN ]