Live data from Hacker News

Stockfighter is live

stockfighter.io

141–150 of 151 posts

Re: Stockfighter is live

#141
post #104

I am not a devops but seriously curious, wouldn't this scalability problem they are experiencing been solved already by using Amazon EC2 and stuff?

not sure if you are joking, since they are using ec2 afaik

okay. so isn't the purpose of that is to auto scale based on system load? Am I missing something?

Re: Stockfighter is live

#142
post #7
post #2

Unable to validate my email. Earlier it wasn't working at all, now it tells me I need to be logged in (but I am, I think). Edit: Fixed for me now.

We had a bug in email validation (worked on staging grumble grumble ). Separately, our deploy script blows away memcached. Guess where email validation tokens were kept. I temporarily turned off bust-cache-on-deploy and the rapidly rising number of validated emails suggests things are working now. Now back to more DevOps craziness.

For email validation you can also just used a signed json token (jwt), so that way the only thing you need to store on your servers is the secret key.

Re: Stockfighter is live

#143
post #128

Earlier quoted context omitted.

I think skipping #5 is unwise. What's to stop someone from making starfighter account, scoring well, and then selling their account to some middling programmer?

What's to stop someone from diving head first down the stairs to speed up their descent?

I think the idea behind starfigher is great. But if I was using their service, I'd do a "Trust, but verify" approach. I would not skip a technical interview. But I also wouldn't bombard them with inane whiteboard challenges or multi-hour take-home challenges

However, I would want them to walk me through their code. And I would want to probe into why they made certain decisions. And I'd like to give them at least one challenge and witness their problem solving process. So #5 would most certainly not be skipped.

But if the expectation of this service is there's absolutely no technical vetting process outside of this game then I guess it wouldn't be a service I'd ever use to hire someone. I don't believe that's the case though.

Re: Stockfighter is live

#144
post #110
post #78

Earlier quoted context omitted.

Modestly less trivial if you happen to put your chat server on the box with Rails because Rails is certainly not going to fall over and your chat server attempts to open several thousand websockets on a box with a not-too-generous number of open file descriptors, it appears.

I feel like a chat server is something best served by something not in your stack (especially Rails). I surprised you chose to do it in house. How about using https://pusher.com/ or https://www.firebase.com/ ?

Perhaps those lack useful vulnerabilities?

Re: Stockfighter is live

#149
post #104

Earlier quoted context omitted.

not sure if you are joking, since they are using ec2 afaik

okay. so isn't the purpose of that is to auto scale based on system load? Am I missing something?

Yes and no. According to Amazon, "EC2 is a web service that provides resizable compute capacity in the cloud." Really, an EC2 instance is just a virtual computer. You can, with the click of a mouse, create a new EC2 instance and load a pre-defined system image onto it. This allows you to, rather quickly, manually increase or decrease the number of EC2 instances based on load. Automatic scaling of EC2 instances can also be done, although it would be provided at a higher layer.

However, a more critical factor is whether the architects designed their systems and software to scale effectively when the number of EC2 instances is adjusted. If there is a bottleneck that is not properly addressed by adding EC2 instances, then adding EC2 instances will be pointless.

Re: Stockfighter is live

#150
post #110
post #78

Earlier quoted context omitted.

Modestly less trivial if you happen to put your chat server on the box with Rails because Rails is certainly not going to fall over and your chat server attempts to open several thousand websockets on a box with a not-too-generous number of open file descriptors, it appears.

I feel like a chat server is something best served by something not in your stack (especially Rails). I surprised you chose to do it in house. How about using https://pusher.com/ or https://www.firebase.com/ ?

[deleted]
Post reply on HN