3 ms·
Ok, if you simply use EC2, S3, maybe a single RDS and/or Elasticache. Ok maybe I agree there. But the real magic comes when you learn to architect entire appli
by maerF0x0 5y ago
Ok, if you simply use EC2, S3, maybe a single RDS and/or Elasticache. Ok maybe I agree there.
But the real magic comes when you learn to architect entire applications out of their pre-built patterns.
random examples OTOH : fan out messages to a number of lambdas when a SNS topic receives a message . processing + backing up a kinesis event stream w/ lambdas + s3. There are many many cross product integrations that make development about as simple as connecting the two ends of a (data) hose. In these sorts of cases you can trade $$ for velocity pretty easily. Yes it will cost you a bit more to operate, but far less than the humans you save.
Also on the argument about unexpected traffic leading to unexpected bills. AWS is most applicable for businesses that have a strong correlation between traffic and revenue. If you make a dollar per million, then it's fine when you wake up to elasticity unexpectedly handling a trillion. Not so much if you don't have an actual business.
- jopsen 5y agoI have mixed feelings too... SNS/SQS are awesome. But if you end up with micro services, your tests won't cover the integration of the entire system.
- maerF0x0 5y agoLayers of testing. You're right that unit tests wont cover the entire system though. Typically the most important customer features will also have other suites that test end to end (API Call goes in, eventually S3 file is generated or something like that) .