Thank you very much for visiting this page it means lot to me.
The whole schema of idea and execution broke down into few paragraph to quick overview.
Parley is Advance version of jaiku.But with little technology enhancement and with new approach to connect people with various purpose.
Each of this days platform is great and unique for various things my idea is not vast(Scope+Resource) but focus on few things.
Jump to credential to use Parley for userJump
This project focus on extreme realtime case
The main aim of this project is to connect high profile personalities such as(Celebrities,Leaders,Politician etc.) will spent their little time for fans or followers to connect in very realtime and talk via audio-video feature based on webRTC
Possible use of as follow(My Perception)
Parley will prove an additional feather to a you in future.
Parley use user-password credential to use feature such as "Go live" to connect people.Twitter verification also used(Twitter-API) for twitter-verfication status to identify celebrity status.
Parley currently deployed on single server to cope up with socket.io nature but can solve by Future balancer idea
Parley top priority work relay on Redis + Array(Node.js)
Currently working on one extra feature that measure people frequency and activity for individual user so in future get priority to talk with celebrity based on his/her consistency
Factors need to consider
This is just initial attempt from my side and have very tiny hardware configuration,but still i tried my best to create a small demonstration
Each function will take average 0.3ms to 6ms to perform redis command:Mostly redis commands are O(1) so there will be no extra time-complexity needed when data-size hype,Only bottleneck is the single server nature and RAM size(#Load_balancer).
This Product does not have any limitation:its my limitation that i can't do more than this
My braking point : Less resource + No money + Nobody will show their interest on individual
Breaking point : Although Parley made under memory proof environment such redis can handle many million entries with rapid access and also no worthless iteration to get or remove from live pool.The breaking point is server memory as user count increase such as million + million fan connection definitely parley need extra server but socket.io limitation comes into picture : "Actually i dont know how to work with multiple server with socket.io but sure reliance does".i am best at single server.
I am a single engineer(jswalker) i have limited hardware resource to make system more stable on million of concurrent users,We have to implement following load balancer technique for parley.
Hardware is everything in this project.
Test on non-dedicated windows pc where half of memory(1.5 GB/3.86 GB) used by various heavy processes
If there is good and stable server with high memory supported system can handle many millions of entries without causing any problem
Now imagine performance on those server where each server contain only redis + Node.js with memory rich server.
Slot:People(Mostly celebrities) book slots(100-1000) for weekend to connect with people
*Advantages of slot policy
*Disadvantages of slot policy
Diplomacy Words:This is will be groundbreaking success of politics adopt such kind of process.Each week/Month politician hear the request or grievance of particular area-city direct from people.
*Advantages of diplomacy policy:
*Disadvantages of diplomacy-policy
Abusive user can be blocked by live user:Feature already present in Parley
Jswalker control module responsible to push development(Local) code to Live(Remote) code
*Advantages of this control module:
*Drawback of this control module:
It is single-entry-exit approach:it means every transaction must pass via jswalker control under one authority.it makes command center for alteration.
Little effort + Little contribution = People will 10X