Scaling Clearbit to 2M API requests per day

Re:Scaling Clearbit to 2M API requests per day by Bonogongo on Monday September 07, 2015 @05:02AM (#10180628)

2M req/day = 2000000/24/60/60 = 23 req/s average. With a assumed peak of 10x of avg. this is around 230 req/s.

Hmm. Not something I'd use the word 'scaling' for, even if there is a 1:1 write to DB ratio. With 1000 writes/sec to a DB it gets interesting.

[ Parent | on HN ]

Re:Scaling Clearbit to 2M API requests per day by MichaelGG on Monday September 07, 2015 @07:08AM (#10180980)

Divide that over 18 machines, too!

I end up doing this with customers. "Well we need a solid hosting system. Our site gets 2 million visits a month!" Me: You know, that'd run alright off my iPAQ. (Actually, with a caching frontend like CloudFlare, it really would.)

Edit: Not to be dissing on their post. I think it's interesting and good that people post such articles. It's just that the sense of scale is off. There was a big article here on some large company, I think it was bitly, and the totals came out pretty low. Especially for the amount of servers. Even Twitter was only peaking at a few KTweets/s a bit ago (granted they do a lot of work per tweet but still).

[ Parent | on HN ]

Re:Scaling Clearbit to 2M API requests per day by Bonogongo on Monday September 07, 2015 @11:44AM (#10181835)

" Divide that over 18 machines, too!"

Yes therefor I'd said DB writes, which is the first step stone where you need to think a little in scaling.

[ Parent | on HN ]