Successor to cloud computing, aka tweelter new architecture

When you have to perform a real big amount of operations you have two options

  • Increase your computational power (like using a cloud solution or scale on more servers)
  • Move your computations to the most available cloud platform of the world: your users
To improve tweelter performances and avoid overloading twitter API we are studying a new computational architecture for tweelter which can return results to the user faster and give less overhead to our servers.
The key to achieve the result is to move most of the search overhead to the computers of the other users currently viewing tweelter, like SETI@home does, by using tweelter you would speed up other users searches and also your own searches.

2 thoughts on “Successor to cloud computing, aka tweelter new architecture

  1. Just one tip: please show who's the author of the blog post…

    Are you looking to build a distributed app, sharing user resources using clients computational power through js? Nice idea… :D

  2. Yes we are looking to implement most of the tweelter computation on client side by using javascript, that might improve performances and overhead of a lot of functions of most web sites.

    Think of client side template engines, you would totally remove server side template generation which is usually a sensible part of your web page generation

    About the author of the post, if you take a look at the home page near the date and time there is the name of the author :D

Leave a Reply

Your email address will not be published. Required fields are marked *