21–29 of 29 posts
I wonder why you would need to add engineers to scale an automated trading platform. Extra features, sure. But scaling? Shouldn't be an issue if things are reasonably designed.
This Kraken which was barely usable during the hype?
Was the "Your transaction might have not succeed, please reload" message designed by you?
I was hoping for something like "don't use an AP NoSQL database for storing your financial transactions". I've always wondered how and why they chose MongoDB.
I wonder why you would need to add engineers to scale an automated trading platform. Extra features, sure. But scaling? Shouldn't be an issue if things are reasonably designed.
Had to take a look at your profile and when I read "Formerly first employee and architect @ Kraken (2011-2015)" I spilled my coffee all over the place. This Kraken which was barely usable during the hype? Was the "Your transaction might have not succeed, please reload" message designed by you?
I wonder why you would need to add engineers to scale an automated trading platform. Extra features, sure. But scaling? Shouldn't be an issue if things are reasonably designed.
At the height of the boom last year, Coinbase was signing up 50,000 new customers every day. Scaling would be a problem for any web app at that level of growth.
I wonder why you would need to add engineers to scale an automated trading platform. Extra features, sure. But scaling? Shouldn't be an issue if things are reasonably designed.
A large class of features are necessary for scaling: those that automate something that previously required a support call. Handling all the KYC verification for every state and country, for example, takes a lot of engineering.
Earlier quoted context omitted.
Had to take a look at your profile and when I read "Formerly first employee and architect @ Kraken (2011-2015)" I spilled my coffee all over the place. This Kraken which was barely usable during the hype? Was the "Your transaction might have not succeed, please reload" message designed by you?
Dear snarky anonymous coward, if you read carefully you would realise that no, that all happened after I left (2015). Bonus reading: https://news.ycombinator.com/item?id=18140251 https://news.ycombinator.com/item?id=18140482
Earlier quoted context omitted.
Dear snarky anonymous coward, if you read carefully you would realise that no, that all happened after I left (2015). Bonus reading: https://news.ycombinator.com/item?id=18140251 https://news.ycombinator.com/item?id=18140482
So your implying that kraken was a great system when you where there and only became a clusterfuck after you left? AFAIK they didn’t decide to exchange a perfectly working and scalable framework for one that was incapable of handling basic functionality for a larger user base during 2016, though I might be wrong. Feel free to enlighten me.
Earlier quoted context omitted.
A large class of features are necessary for scaling: those that automate something that previously required a support call. Handling all the KYC verification for every state and country, for example, takes a lot of engineering.
My impression was most businesses in the space outsource this to specialist providers for legal reasons before and above internal process scaling reasons.