My job as a TL is to think through the consequences of decisions. I understand your use case is solv
My job as a TL is to think through the consequences of decisions. I understand your use case is solved by the requirements you laid out but we don't build features just for 1 customer unless it's a very large ENT contract (& even then, maybe). I need to think through the problem comprehensively so that the feature is designed in a way that doesn't lead to a dead end or have sharp corner cases that surprise customers that aren't you in weird ways.
This is a cost reduction mechanism but only for the customers that can make use of it (& even then, storage is fairly cheap - I don't know how big of a cost reduction this is in practice).
AFAIK no other object storage system has something like this. That gives me pause and makes me want to make sure I've thought through every potential corner case & know how it should work.
This is a cost reduction mechanism but only for the customers that can make use of it (& even then, storage is fairly cheap - I don't know how big of a cost reduction this is in practice).
AFAIK no other object storage system has something like this. That gives me pause and makes me want to make sure I've thought through every potential corner case & know how it should work.
