Deschide articolul original într-un tab nou Schimbarea acestei opțiuni se aplică imediat și reîncarcă pagina.
LECTURA
Înapoi la articole →

Prateek Codes - Building Scalable Backend Systems

prateekcodes.com/feed.xml
Vizitează site-ul

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 11

  1. 'Can Jane open this file?' asked millions of times a second, across nested groups. How Google's Zanzibar answers it fast

    (Prateek Codes - Building Scalable Backend Systems)

    Every product with a share button asks the same question constantly: can this user see this thing?

  2. Multi-hop delegation for AI agents: porting OAuth's on-behalf-of pattern into MCP topologies

    (Prateek Codes - Building Scalable Backend Systems)

    Most AI agent deployments hit an awkward authentication problem inherited from web auth.

  3. Stop Pasting Schema Into Your AI: Connect PostgreSQL Directly with MCP

    (Prateek Codes - Building Scalable Backend Systems)

    Agentic coding tools have gotten good at reading your codebase.

  4. Rails 8.2 adds this_week?, this_month?, and this_year? to Date and Time

    (Prateek Codes - Building Scalable Backend Systems)

    ActiveSupport already has today?

  5. Read-only database MCPs as a scoped-delegation pattern: applying IAM primitives to AI agents

    (Prateek Codes - Building Scalable Backend Systems)

    AI agents are useful in proportion to the context they can read.

  6. Rails 8.2 lets retry_on read the error when calculating wait time

    (Prateek Codes - Building Scalable Backend Systems)

    Active Job’s retry_on accepts a wait: proc for custom backoff logic.

  7. Ruby::Box Practical Guide: Use Cases and Integration Patterns (Part 2)

    (Prateek Codes - Building Scalable Backend Systems)

    In Part 1, we covered what Ruby::Box is and how it provides namespace isolation.

  8. Ruby 4.0 Introduces Ruby::Box for In-Process Isolation (Part 1)

    (Prateek Codes - Building Scalable Backend Systems)

    Ruby 4.0 introduces Ruby::Box, a feature that provides isolated namespaces within a single Ruby process.

  9. Rails 8.2 makes enqueue_after_transaction_commit the default

    (Prateek Codes - Building Scalable Backend Systems)

    Rails 7.2 introduced enqueue_after_transaction_commit to prevent race conditions when jobs are enqueued inside database transactions.

  10. Rails 7.2 adds enqueue_after_transaction_commit to prevent job race conditions

    (Prateek Codes - Building Scalable Backend Systems)

    Scheduling background jobs inside database transactions is a common anti-pattern which is a source of several production bugs in Rails applications.

  11. Rails 8.2 introduces Rails.app.creds for unified credential management

    (Prateek Codes - Building Scalable Backend Systems)

    Applications often store secrets in both environment variables and encrypted credential files.