←back to thread

Ask HN: How to study for system design that doesn't include front end/back end?

38 points 3a2d29 | 1 comments | 13 Mar 25 23:32 UTC | HN request time: 0.231s | source

I got a system design interview where I was asked to build a pricer for a financial product, then expand it to multiple pricers that might share inputs.

This was not the typical system design interview where you have to deal with APIs / load balancers / latency / etc

I have studied that a lot, but what about these type of general interviews?

1. sgentle ◴[14 Mar 25 04:26 UTC] No.43359564[source]▶
I learned a lot about event-driven distributed systems by just building things with ZeroMQ. Even if you don't end up using it, learning its messaging patterns and the decisions behind them can give you a pretty solid mental framework.

The ZeroMQ guide really takes you through it in detail, for example check out Figure 19 here for a parallel job queue with cancellation: https://zguide.zeromq.org/docs/chapter2/#Handling-Errors-and...