4 ms·
No, for the same reason it still doesn't make sense to go with AWS. Basically you need a large number of cores that are intimately integrated amongst a large qu
by ChuckMcM 13y ago
No, for the same reason it still doesn't make sense to go with AWS. Basically you need a large number of cores that are intimately integrated amongst a large quantity of storage. It was the fact that all the machines could have a bunch of drives on them for "free" (low marginal cost). By interspersing the data and the compute you get maximum bandwidth to local assets.
- wmf 13y agoIsn't that how EC2 works?
- mwcampbell 13y agoIf I understand correctly, the problem is that persistent storage (either S3 or EBS) is network-attached, and you pay by the gigabyte and by the number of requests or IOPS.
- mwcampbell 13y agoWhat classes of applications benefit from that level of integration between processing and storage? It strikes me that both AWS and various PaaS providers (especially Heroku) encourage strong separatioin between the application and its storage. Applications are supposed to treat all persistent storage as network-attached, while the VMs or containers running the appliication are ephemeral. I guess you're saying this is untenable for some kinds of application.