4 ms·

> But it's possible this migration process would have been easier if we had done it sooner. What the f*? Of course it would have been easier if you had done it

> But it's possible this migration process would have been easier if we had done it sooner. What the f*? Of course it would have been easier if you had done it sooner. What you lacked was the willpower from decision-makers who had growth of dollar-signs in their eyes. You've littered this thread with comments explaining how every move you made was based on ROI. That's the kiss of death for architecture concerns, and bizarrely it puts Node.js on the list of runtimes for data/stream processing backends. No matter how many times you explain how you made these decisions, I can't help getting the feeling you were wearing horse blinders. Edit: I find it impossible to imagine that nobody on the engineering team ever shouted, Hey look out! We are basically a Web farm for banking-related requests, this is insane! Surely you've heard from those people and they were let go.

bjacokes 7y ago
I say "possible" because our system observability was less mature even 12 months ago. Firefighting 10 different root causes of memory or event loop issues without the right tooling in place would be a nightmare. That's why we did a deep dive into the tooling that we considered to be a prerequisite for this project – hopefully it's helpful for others in our situation. Different companies make different decisions when weighing ROI against architecture concerns. We're heavy on pragmatism and impact at Plaid, so it's quite intentional that we don't fall all the way on the latter end of the spectrum. I appreciate the discussion in the comments as to how effectively we are balancing these two concerns – certainly this is an area where reasonable people can disagree.
- ubu7737 7y ago
  It's an organic difference of perspective, which is why (you're quite right [that]) reasonable people can disagree. But the fact remains that you've built a golem with clay feet. There's a deep imbalance in your prospect. Edit: engineer to engineer: you have to start over.

bjacokes 7y ago

I say "possible" because our system observability was less mature even 12 months ago. Firefighting 10 different root causes of memory or event loop issues without the right tooling in place would be a nightmare. That's why we did a deep dive into the tooling that we considered to be a prerequisite for this project – hopefully it's helpful for others in our situation. Different companies make different decisions when weighing ROI against architecture concerns. We're heavy on pragmatism and impact at Plaid, so it's quite intentional that we don't fall all the way on the latter end of the spectrum. I appreciate the discussion in the comments as to how effectively we are balancing these two concerns – certainly this is an area where reasonable people can disagree.

ubu7737 7y ago
It's an organic difference of perspective, which is why (you're quite right [that]) reasonable people can disagree. But the fact remains that you've built a golem with clay feet. There's a deep imbalance in your prospect. Edit: engineer to engineer: you have to start over.