https://blog.rtshkmr.com/tags/fundamentals/Recent content in Fundamentals on An observer's logHugoenhttps://blog.rtshkmr.com/reference/archi/patterns/fundamentals/statelessness/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/statelessness/<p>🔴 P0 &mdash; <em>appears in nearly every system design interview</em></p>https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/idempotency/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/idempotency/<p>🔴 P0 &mdash; <em>critical for payment systems, Stripe&rsquo;s public API design is built on this</em></p>https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/failure-and-partial-failures/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/failure-and-partial-failures/<p>🔴 P0 &mdash; <em>the defining characteristic of distributed systems</em></p>https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/fallacies/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/fallacies/<p>🟠 P1 &mdash; <em>Peter Deutsch&rsquo;s eight fallacies; useful as a shortcut reference in interviews</em></p>https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/estimation/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/estimation/<p>🔴 P0 &mdash; <em>expected in every system design interview; grounds design decisions in numbers</em></p>https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/fundamentals/