3 ms·
The pricing model seems like it could be a big win for heroku, phpfog, and anyone else arbitraging EC2. Edit: My reasoning is that currently EC2 performance suc
by snissn 16y ago
The pricing model seems like it could be a big win for heroku, phpfog, and anyone else arbitraging EC2.
Edit: My reasoning is that currently EC2 performance sucks and is reliably inconsistent, and if you can spend a fixed price to ensure that you're actually getting what you're paying for, as an ec2 arbitrator, your clients are going to be a lot more satisfied
Edit 2: Ah i see, i misunderstood
- amock 16y agoHow would this be useful to them? I don't think they care if their instances are on the same box or not. Also, how is what Heroku and PHP Fog arbitrage? They're just providing a service on top of another service; they don't even work with multiple markets.
- tlrobinson 16y agoI think you're misunderstanding the pricing model. AWS is charging $10 per hour on top of the regular per instance charges, because if you have a small number of instances they may have to dedicate entire machines to your small instances. As you increase the number of dedicated instances they can put more of your instances on your dedicated machines, recovering the wasted resources. Heroku and other multitenant PaaS services have no reason to use dedicated instances... customers concerned about running on multitenant platforms wouldn't even consider them in the first place.