(Then, something more complex or special purpose, like say Amazon Elastic Transcoder or something).
(Then, something more complex or special purpose, like say Amazon Elastic Transcoder or something).
Due to the hilarious nature of the business, getting an S3 account to use for 'local' (i.e. dev machine) development was a huge chore.
We wound up creating an Interface to abstract our usage of S3, and wrote a 'local' provider that just used the local filesystem. Of course, many use cases that would not work....
But the big -advantage- of it was, we at least knew that if we ever wanted to switch away from S3, it wouldn't be hard. The Interface had a spec that could be used to ensure that any plugin would work with our application's usage.
It wasn't -that- much more work.
Which violates these requirements, right? Using something that mocks S3 instead of actually being S3?
(If I was going to do that, I'd just use open source Minio S3 clone, assuming it adequately cloned the S3 features I needed).
All that said, I agree with the sentiment of the post, testing the system as a whole can reveal issues before they get to prod. But maybe that means you need to harden your contracts and internal SLAs.
This can probably work with more complex services too.
But I'm not sure that would comply with the requirements, they seem to forbid running against external services at all, no? '"calling out to a few hard-to-run external services" doesn't count.'
I think every team needs to decide how much to follow the original advice, there is certainly a balance between simulating external service locally (with possible associated behavior changes) or using an external service.
If you do want to run everything locally, there are servers which offer S3 API, like "minio" and "fake_s3". Probably would be very nice for localhost operation. But if you need a complex thing like Transcoder this is not going to work.
Not usually available for most other AWS services you might be using though. Say, Elastic Transcoder for transcoding A/V media.