|
|
|
|
|
|
by slver
1889 days ago
|
|
|
My impressions TLDR: 1. "Built for delight" Author wants everyone to suddenly start making nicer things. 2. "Truly serverless" Author wants to throw code at cloud, without thinking about performance or resource usage. 3. "Fast" Author wants every AWS command to take less than a second. 4. "Ephemeral resources" Author wants to test in the cloud with less effort. 5. "Code not configuration" Author doesn't like static config, everything should be an API. 6. "Built for productivity" Author wants everyone to be more productive. All in all, reads a bit like the random musings of a frustrated cloud server user. |
|
|
Not really what Erik is saying. Taking AWS S3 as an example, you absolutely need to think about performance and resource usage when dealing with S3, but you never have to think about the servers. You never think about some cluster that is making your S3 usage possible.
S3 is such a great success that there's very few (if any) examples of companies starting with S3 and then getting too big for it and needing to build their own system (thus wrangling servers and clusters etc). Dropbox migrated off of S3 to 'Magic Pocket' but I'm pretty sure this was for $$ reasons not because AWS simply couldn't handle Dropbox's massive read+write requirements. AWS S3 is a marvel of serverless computing, and we should try and get more like it.