An Update from Robinhood’s Founders
blog.robinhood.com
An Update from Robinhood’s Founders
1–10 of 295 posts
Re: An Update from Robinhood’s Founders
#2Re: An Update from Robinhood’s Founders
#3Re: An Update from Robinhood’s Founders
#4Re: An Update from Robinhood’s Founders
#5Re: An Update from Robinhood’s Founders
#6Re: An Update from Robinhood’s Founders
#7Their DNS system failed? How?! Unless DNS stands for “Do Not Sell”
Why? Well that tiny DNS server has certain capacity constraints and if you don’t cache DNS lookups by using a http/https agent for example (in NodeJS) you wind up looking up the same dns info over and over and churning sockets like it’s going out of style. If you run really really hot the poor thing falls over (rightly so).
The limits are high and DNS is fast so you usually don’t notice but when you are under load bugs like this come out of the woodwork. When it falls down you look up the AWS docs, lean back in your chair upon finding this isn’t an “elastic” part of AWS and say “FUUUUUUUUCK” so loud it can be heard from outer space.
If you are Robinhood though don’t you have some former Netflix SRE/DevOps beast on staff that knows this and so you run your own DNS and monitor it?
Re: An Update from Robinhood’s Founders
#8This blog post doesn't appear to say anything. It's not an apology, it's not an explanation, it doesn't say what they're going to do in response.
This is after the incident in which there was no status updates or support availability for multiple hours of time. Why can't they commit to updates every hour or every 30 minutes?
Re: An Update from Robinhood’s Founders
#9Is every bitcoin company run by ex cellphone store employees? Just the exchanges?
Re: An Update from Robinhood’s Founders
#10wasnt this cause by leap year and them not taking that into account?