1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

best technology for server side matchback

Discussion in 'Programming' started by yknot7, May 10, 2011.

  1. yknot7

    yknot7 New Member

    Joined:
    May 10, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    Hi -

    I am looking at alternate technologies to solve this -

    1) Multiple user computers send me information from my program that runs on their computer every couple of seconds
    2) I need to match it to similar data that other users have relayed in the last 3 minutes and if it matches send both users a notification
    3) when i receive new information from the user it needs to clear the old information and do the same for the new information.

    I need something that is instantaneous and constantly runs for over 100,000 users.

    Any suggestion will be helpful

    Thanks and regards
     
  2. shabbir

    shabbir Administrator Staff Member

    Joined:
    Jul 12, 2004
    Messages:
    15,292
    Likes Received:
    365
    Trophy Points:
    83
    Is your server that much powerful to handle 100k concurrent users? What is the configuration of your server then?
     
  3. yknot7

    yknot7 New Member

    Joined:
    May 10, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    I am on the amazon cloud, right now I have only 100 users but scaling really fast & the DB batch that we run constantly is beginning to slow down.
     
  4. shabbir

    shabbir Administrator Staff Member

    Joined:
    Jul 12, 2004
    Messages:
    15,292
    Likes Received:
    365
    Trophy Points:
    83
    If you are on Amazon cloud you can always scale up with a new instance of the server to handle.
     
  5. yknot7

    yknot7 New Member

    Joined:
    May 10, 2011
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    Guys I am not dumb and yes I can scale as I am on the cloud.... But it also costs me a lot more that maybe re-writing the entire back end in a more efficient way

    Thanks
     

Share This Page