Hacker News new | ask | show | jobs
by cookiecaper 3365 days ago
While I respect the process involved in putting so many moving parts together, sometimes I wonder why we have to complicate these things so much.

From my reading of the flow chart, it appears that data jumps through 5 different data layers before it gets written in its final destination. This doesn't appear to be a transformation pipeline, that's just how much it takes to go from user input -> saved in indexed storage.

What unique featureset does WePay provide that justifies this type of complication?

As an industry, there's been an explosion of this massive overcomplication the last few years. We're contorting ourselves pretty bad here, and it seems primarily to be in service of the engineer's desire to, well, engineer. Can you imagine if we let road engineers get away with this kind of stuff?