Re:The Amazon Premium
by the_gipsy on Thursday December 19, 2019 @12:55PM
(#21837350)
How does your development cycle look like? For example, you decide you want to add S3 or Redis. So you add it to some yaml, or do it in the amazon console. How do you develop/test/debug the code that would use these services, locally, before pushing that to production?
[ Parent
| on HN ]
Re:The Amazon Premium
by kugelblitz on Thursday December 19, 2019 @02:15PM
(#21838196)
I try to abstract something like the filesystem. So I would use something like Flysystem for PHP, or pyfilesystem for Python where an environment variable would decide whether it's saved to local disk or S3.
For some more difficult use cases I have to be pragmatic and decide on the circumstances. E.g. when needing presigned URLs (which is an S3 feature) I will use the native S3 SDK, it's not the cleanest way, but it gets the job done. Only when it starts getting annoying / slowing the development speed will I abstract it away. Security is important and I keep a high standard there, but when it comes to clean abstraction I will occasionally make compromises, knowing that often we will only need one implementation or that feature might be thrown away (I work freelance mostly with startups or SMEs).
Thank you. BTW I agree with starting simple and only abstracting if necessary.
Re:The Amazon Premium
by potta_coffee on Thursday December 19, 2019 @07:31PM
(#21840746)
Amazon recommends "testing at scale", basically spin up a non-production version of your architecture and try it out.