> Resizing and watermarking images on the fly using caller-specific details, such as the user who requested the object.
Now we need to either do rescale directly after storing or need to use another service (on EC2) to do the resize. With Object Lamda, we could do it on-the-fly as the user calls the image. This is operational a lot easier.
Advantage here is that clients can just continue to use their existing S3 interface yet your lambda is still invoked.
Edit: I guess you meant that cloudfront caches it for you automatically.
I start my data as .csv.gz but the first step is a CTAS to extract columns and convert to compressed parquet. This step basically costs the most but gives a 10x data size reduction to downstream steps.
Athena does not work at all if you perform large numbers of small indexed read queries, definitely use a traditional database for that.
I did never work with it, but there is Athena that allows to query S3 in something like SQL. I think there _might_ be some cases were S3 is a useful database, as one can use pre-signed URLs to let any client write to the database (S3). That‘s something I‘m not sure how to set up with a classic database and without any API in between.
IMHO, I think it‘s all about the same functionality with a simpler architecture.
With this we might simplify the pipeline because we can keep the same S3 interface.
I guess that for some systems that are heavily S3-based it will help adding new features without needing to rewrite the interface or duplicate the functionality.
It's nice to know that AWS achieved such lock-in with some customers.
The lock-in mechanism. Imo this isn’t more functional than other approaches, it’s a way to ensure you don’t switch services.
It's not clear to me what the real benefits of Object Lambda provides. Indeed it could move your transformation code closer to its data, but the cost of doing that is the management and complexity of the lambdas. I am curious what a best use case example would be for this.