हर उम्मीदवार को एक ही तराज़ू पर.

• PSPriya S.मज़बूत

  We had a read-heavy path that kept falling over at peak, so I split the write path onto its own service and put a read replica behind a cache — it bought us about eighteen months of headroom.

  00:12:04ट्रांसक्रिप्ट में
• TRTomás R.मज़बूत

  I'd start by asking what the read-to-write ratio actually is, because sharding a table nobody reads twice is just operational cost. Then I'd look at where the contention is.

  00:09:41ट्रांसक्रिप्ट में
• WLWen L.आंशिक

  Honestly the design was handed to me. I owned the rollout rather than the architecture, so I can talk about what broke more than why we chose it.

  00:14:22ट्रांसक्रिप्ट में
• ANAdaeze N.मज़बूत

  We were writing patient events twice, once for audit. I moved audit onto a log-structured store and made the primary path append-only, which killed a whole class of consistency bugs.

  00:11:07ट्रांसक्रिप्ट में

ऊपर की हर पंक्ति उसी इंटरव्यू से उद्धृत है जहाँ से वह आई। यहाँ कुछ भी किसी उम्मीदवार को अंक नहीं देता, क्रम नहीं लगाता और बाहर नहीं करता — वह पैनल करता है, इस बार सबूत सामने रखकर।