For the best performance naming many small files in an s3 bucket may not be the best idea unless they user_id is a random string. See how the S3 hashing algorithm works https://aws.amazon.com/blogs/aws/amazon-s3-performance-tips-tricks-seattle-hiring-event/
So replacing it by a random hashed value may not be that bad. Of course you need to store the hash in ...
It is possible to do this (not with any built-in steps; you essentially have to either use a global cache or write your own caching tool), but I do not recommend it. When I've tried this in the past, I often ran into race conditions. For example, one build would write to the cache while another build simultaneously reads from the cache, or two builds would ...
Check the image history of your two images with docker image history. Pay careful attention to the sha256 checksum of the files being added on the ADD line. Docker performs a checksum on the files, including some of the metadata on these files, so a single byte change or a permission update will result in a cache miss.
Once you've checked this, if it is not ...
The default location of the image cache is under /var/lib/docker.
The "cache" features in docker are more like a communication vehicle for the documentation, than a proper, separate data structure. There is no special storage which makes up this cache.
For every filesystem-modifying line (RUN/ADD/...) in your Dockerfile, docker run ...
Dude, will depends of what you want to use or follow. Actually cloud + DevOps it's a buzzword in use.
So you can start reading about Cloud Architecture, Modern Infrastructure.
Refer about one book, maybe these: https://www.springer.com/gp/book/9783030037116
Redis Cluster could be considered as an OOTB solution for the Scalability requirements. There is another interesting open source library known as Redis Shard for sharding implementations on Redis. Please find the GitHub repository here.
Adjust Jenkins job "Build Environment"
also add build step with shell/windows script with
npm install -D