What is RevS and how does it concern me?
Today,most apps/online services still use centralized servers,which is really spendy,and it's ugly when it goes down.If you've made one,you'd know what I'm talking about.Refresh a list?Ask the server.Download a file?Server.Send a message?Server again.Ugh.
But what else have we got?The answer is peer-to-peer.You've seen it in BitTorrrent,Gnutella.P2P allows developers to build networks without centralized servers. It has tons of advantages over centralized networks: Less building cost,Less maintenance cost,More dynamic,Harder to go down ,and more.
For individual developers,it can save butt loads of money,allowing them to innovate better.
For enterprises,they can throw away those gigantic servers,and keep only one or two small servers.
For users,adopting RevS means they can use the online services even when the servers are down.Amazing.
RevS can dramatically reduce the costs for online service developers.
A different edge
Most P2P applications today are only for sharing files,but we do not recommend you to build another one of them,because P2P is so much more than just fiddling with files.You see,a P2P app is capable of doing most of what a server-client app can do,and a lot better at it.RevS could replace the old networking part in server-client apps,and it's also good for building new kinds of apps with P2P logics.
Easy to learn,easy to use
Sure,there are other P2P implementations,but if you've seen one or two,you would know that they are complicated and sometimes specialized.You can't really figure out what you can actually do with them,and that's why a lot of programmers gave up P2P. But not RevS.RevS offers a straight forward logic and an easy-to-use API that can surely change your idea about P2P programming. And you can upload and download files just like interacting with a server.If you are familiar with building server based apps,you'd feel like you're home.
GitHub Page:
https://github.com/theGreatLzbdd/RevS
Today,most apps/online services still use centralized servers,which is really spendy,and it's ugly when it goes down.If you've made one,you'd know what I'm talking about.Refresh a list?Ask the server.Download a file?Server.Send a message?Server again.Ugh.
But what else have we got?The answer is peer-to-peer.You've seen it in BitTorrrent,Gnutella.P2P allows developers to build networks without centralized servers. It has tons of advantages over centralized networks: Less building cost,Less maintenance cost,More dynamic,Harder to go down ,and more.
For individual developers,it can save butt loads of money,allowing them to innovate better.
For enterprises,they can throw away those gigantic servers,and keep only one or two small servers.
For users,adopting RevS means they can use the online services even when the servers are down.Amazing.
RevS can dramatically reduce the costs for online service developers.
A different edge
Most P2P applications today are only for sharing files,but we do not recommend you to build another one of them,because P2P is so much more than just fiddling with files.You see,a P2P app is capable of doing most of what a server-client app can do,and a lot better at it.RevS could replace the old networking part in server-client apps,and it's also good for building new kinds of apps with P2P logics.
Easy to learn,easy to use
Sure,there are other P2P implementations,but if you've seen one or two,you would know that they are complicated and sometimes specialized.You can't really figure out what you can actually do with them,and that's why a lot of programmers gave up P2P. But not RevS.RevS offers a straight forward logic and an easy-to-use API that can surely change your idea about P2P programming. And you can upload and download files just like interacting with a server.If you are familiar with building server based apps,you'd feel like you're home.
GitHub Page:
https://github.com/theGreatLzbdd/RevS
