I suppose so but I doubt that the AMAgeddon will have caused enough users to permanently leave Reddit altogether for them to need to downsize.
The difference between the AMAgeddon and the Digg collapse is that Reddit already had its own stable site that could handle the massive influx (whereas Snapzu is invite only and slowing the flow of new users and Voat has had its bandwidth annihilated), already had its own developed culture and a better community (the joke on Reddit at the time is that Digg would get whatever was on the front page 2 days later) and had site functions that where better / expanded upon what Digg had already done.
I think that the site that will become "The Reddit Killer" will at least need to satisfy the following points.
For database it depends, for redis and memcached you have elasticcache. For SQL databases it will depend on the architecture of your application and your sharding strategy.
True, it always depends, but unless the devs planned for this in their architecture, they'll have a greater bit of difficulty scaling up their data storage and retrieval compared to webservers.
Look at the guy from Vaot, he started the site as an expermient to learn ASP.NET and C#. I don't know how skilled the devs are behind this site, but it wouldn't surprise me if scaling to millions of users was not at the top of their heads when starting out. Hell, even sites like Twitter had immense problems because the initial idea wasn't built to scale, nor should it have been. YAGNI and all that.
They obviously have a lot of servers running the place, do you think that with less traffic and in turn less ad revenue they'll downsize?
I suppose so but I doubt that the AMAgeddon will have caused enough users to permanently leave Reddit altogether for them to need to downsize.
The difference between the AMAgeddon and the Digg collapse is that Reddit already had its own stable site that could handle the massive influx (whereas Snapzu is invite only and slowing the flow of new users and Voat has had its bandwidth annihilated), already had its own developed culture and a better community (the joke on Reddit at the time is that Digg would get whatever was on the front page 2 days later) and had site functions that where better / expanded upon what Digg had already done.
I think that the site that will become "The Reddit Killer" will at least need to satisfy the following points.
They are hosted on AWS, they can upscale and downscale on demand.
For webservers yes, you can turn on more vm's to handle more requests. But I don't think that's an option for their database.
For database it depends, for redis and memcached you have elasticcache. For SQL databases it will depend on the architecture of your application and your sharding strategy.
True, it always depends, but unless the devs planned for this in their architecture, they'll have a greater bit of difficulty scaling up their data storage and retrieval compared to webservers.
Look at the guy from Vaot, he started the site as an expermient to learn ASP.NET and C#. I don't know how skilled the devs are behind this site, but it wouldn't surprise me if scaling to millions of users was not at the top of their heads when starting out. Hell, even sites like Twitter had immense problems because the initial idea wasn't built to scale, nor should it have been. YAGNI and all that.
Oh OK. Cool. Makes it an easy decision then if it's so eaay