Twitter is spending over $15M/month on server costs alone to support 333M active monthly users.
Now compare to Pokemon Go's huge explosion of 20M daily users from a while ago.
This problem is only going to get worse with another 5B+ people coming online into the 2020s.
In order to scale, using (what you call) "fog computing" will be absolutely necessary. Cloud services will still be used, of course, but they will be built as P2P systems to take advantage of the "fog".
Cloud infrastructure will always be around, but how apps are built will be a fundamentally different architecture. But when S3 goes out, like it did the other week, we can't suffer worldwide downtime - that will be unacceptable.
Rethink's unfortunate failure to capitalize in this market is a signal that Master-Slave databases (even the best of the best) will have a very small role with respect to the total amount of data flowing through the internet.
Now compare to Pokemon Go's huge explosion of 20M daily users from a while ago.
This problem is only going to get worse with another 5B+ people coming online into the 2020s.
In order to scale, using (what you call) "fog computing" will be absolutely necessary. Cloud services will still be used, of course, but they will be built as P2P systems to take advantage of the "fog".
Cloud infrastructure will always be around, but how apps are built will be a fundamentally different architecture. But when S3 goes out, like it did the other week, we can't suffer worldwide downtime - that will be unacceptable.
Rethink's unfortunate failure to capitalize in this market is a signal that Master-Slave databases (even the best of the best) will have a very small role with respect to the total amount of data flowing through the internet.
My thoughts here: https://hackernoon.com/the-implications-of-rethinkdb-and-par...
As well as my the Changelog podcast interview: https://changelog.com/podcast/236