I know you were asking for effect, but of course they do and it's EC2. That's why they have a heavy reservation pricing tier, which only makes sense for 24/7/365 (you pay for hours even if you don't use them).
But, it's fun to point at "elastic" and tell people they're "doing it wrong" because they don't take a name chosen 7 years ago literally. As if somehow the service (called EC2 virtually everywhere -- not Elastic Cloud Compute) could never evolve beyond that initial use case. Incidentally, the "elastic" in EBS must have a different meaning because one of its primary selling points is that it's persistent storage.
In other words they took a system targeted especially at people who needed on-demand computing and as it got popular, adapted it to the needs of the 24/7/365 web-hosting by offering an alternate pricing model, point-and-click user interfaces and additional features and services like EBS and CloudWatch.
The point is absolutely not that EC2 never evolved beyond its initial use case and isn't good at other things.
The point is that while they have 24/7/365 hosting services, there's never been any reason to expect that they would be better at it than anyone else. So why do we continue to see blog posts about not liking EC2 with vague complaints about the horrible price-to-performance ratio getting lots of upvotes?
Because EC2 still seems to be a lot of people's default option for 24/365 servers, even though it isn't particularly good for it. Why is that so? Evidently there haven't been enough blog posts on the subject yet!
But, it's fun to point at "elastic" and tell people they're "doing it wrong" because they don't take a name chosen 7 years ago literally. As if somehow the service (called EC2 virtually everywhere -- not Elastic Cloud Compute) could never evolve beyond that initial use case. Incidentally, the "elastic" in EBS must have a different meaning because one of its primary selling points is that it's persistent storage.