A healthtech catalog can generate several derivatives from one product photo. Storing every size indefinitely is a storage decision; generating one on every cache miss is a capacity decision. TL;DR: start with Sharp in your own service when image volume is predictable and you control the build. Choose hosted processing when native builds or batch throughput become the bigger operational burden. The hosted call removes a native dependency but adds a network hop. Neither choice makes cache design ...