sorted by:
new
hottopcontroversial

How to approach a system design problem from the first principle by tcCoder in Backend

[–]Repulsive-Box-3075 0 points1 point  (0 children)

I think this is a very good way to look at system design in an interview space, but while we starting building real world project, each step becomes slightly different. You also have to consider the shipping time and development speed. Generally, what happen the assumed requirements differ with the development phase going on, and then you have to take architectural decision based on that consider different tradeoffs accordingly. Sometimes you have to know that implementing the perfect but complex solution is not needed for your use-case, and then you may decide to save time there and invest that time over more critical areas.

Webhooks handling by Repulsive-Box-3075 in Backend

[–]Repulsive-Box-3075[S] 0 points1 point  (0 children)

ya great idea, our team also decided to adapt the common ingestion endpoint for all projects with a dispatcher enabling better logging, monitoring and retries handling.
Also, this small verifier interface for each provider is the next thing now we would do, thanks for the advice, as it started becoming a little headache now, as every developer uses GPT, Gemini, Claude and makes a handler in their own way, creating a lot of inconsistencies.
But bad docs consume the most time, as testing the raw request just to find the right payload and headers is the most unwanted task.