"Serverless back end" is an oxymoron, I know. But hear me out.<p>Serverless apps are awesome. They're easy to make and are super stable. Yet some features like blog comments we outsource to 3rd party servers that put adware and trackers on our websites. Analytics companies sell your data. We don't like this, yet paying for such a service is overkill for a blog with 100 visitors a month (IMO).<p>Here's what I propose.<p>Servers are needed mainly for data saving. Comments and analytics are frontend modules that need a database. So how about we save the data on a public blockchain. But not on a currency based one, because I am sick of that shit.<p>1. The blockchain can save any type of data (with limited length).
1. All you need to do to use the service is embed a <script> to your site (just like Disqus).
1. Service is free - until current servers are overloaded
1. When overload happens the top n% highest load domains are asked to start running a server OR pay $10/month so someone else would run the server for you.
1. If domain doesn't comply the service is disabled and next n% is asked.
1. Perhaps the data needs to be distributed so there's no single 1TB chain.
1. It's open source and a for-community project (as in not for profit and no getting rich).<p>The idea is that it's a naturally growing network of blockchain hosts. As usage increases the heavy users have to put some effort in to keep using it and thus supporting lower usage apps. The system will never get overwhelmed (unless usage increases too fast) and yet there is plenty of free tiers to go around.<p>Clearly a raw idea, but you're welcome to think with me or just blatantly tell me why this will never work. I've made a chat if this idea seems good enough that you want to help: https://gitter.im/distributed-serverless-backend (I'm going to sleep now, but will read every comment and all of the chat tomorrow.)