By Chason ArthurRevision 118.063Published Updated

PHP / Laravel components / SQL transactions

Sell the last item once.

One item. Two shoppers. A repeated request. Follow the database records through the failure, then try the same event with a stronger design.

The idea in plain language

A transaction keeps related database writes together. A guarded update protects availability. An idempotency key identifies a repeated decision. These mechanisms solve different parts of the same ordering problem.

The browser executes actual PHP and SQLite through the open-source PHP.wasm runtime from WordPress Playground. Each run creates a new memory database. The last-item example replays a chosen stale-read order; it does not measure MySQL concurrency or InnoDB row locks.

Your independent testing environment

Make the failure visible.

Choose “Two shoppers, one item.” Run without safeguards and inspect the two saved orders. Turn safeguards on and see the second reservation declined. Reset starts over and stops pending work.

Ready to try

—Items left
—Orders saved
—Outbox events
—Delivery receipts

Follow the decision

    Inspect the result

    Your result and database records will appear here.

    Why the change matters

    Draw the stale-read timeline. Identify the invariant each database mechanism protects. Explain why an outbox event may be delivered more than once and what the receiver must guarantee.

    Use the code viewer to inspect the original source that produced this release. Each file is checked against the release manifest before it is displayed. The complete download includes the runnable example, tests, setup instructions and third-party notices.

    Download this lab

    Keep exploring

    Follow the question you have next.

    Build the safeguards

    Eight explained steps, tradeoffs, pitfalls and a checkpoint before moving on.

    Read the tutorial

    Compare the choices

    Choose a pattern and an environment for the problem you actually have.

    Compare approaches

    Questions before you start

    Do I need to know how to code?

    No. Start with the default example, read the trace and compare the two implementations. The tutorial introduces the code after you have seen the result.

    Does this use real customer data or send anything?

    No. Examples use invented records and simulated downstream work. Each lab keeps its own transient environment; resetting it stops the experiment.

    What can this experiment prove?

    The browser executes actual PHP and SQLite through the open-source PHP.wasm runtime from WordPress Playground. Each run creates a new memory database. The last-item example replays a chosen stale-read order; it does not measure MySQL concurrency or InnoDB row locks.

    Can I use or change the source?

    The original lesson and application source are MIT-licensed. Third-party runtimes retain their own licenses. Download the package and follow GETTING_STARTED before changing it.

    Lab discussion / PHP Transaction Lab

    What would you try next?

    Ask about the code, compare an approach, or describe an edge case. Reader comments are reviewed before publication.

    All lab discussions

    Reader comments

    Open the discussion to read and add reader comments.

    Read or write a comment →

    Code walkthrough

    Follow the implementation in code.

    These short excerpts connect the lab’s behavior to its implementation. Each example links to the full tutorial step for its context, tradeoffs and checkpoint. Names and dependencies belong to that source; the excerpts are not standalone programs.

    Example 01 · Tutorial excerpt

    Move the availability decision into the database

    The guarded statement subtracts stock only if enough stock exists at the instant of the update. The affected-row count is the result of that decision. An accepted order is written only when one inventory row changed. This avoids the stale application check demonstrated in Step 1. It is appropriate for this single-SKU counter.

    UPDATE inventory
    SET stock = stock - ?
    WHERE sku = ? AND stock >= ?;

    Read the full tutorial step

    Example 02 · Tutorial excerpt

    Give retries an identity

    A retry key identifies one logical request, not one network attempt. reserve checks the prior request inside the transaction before checking current availability. It compares a hash of the normalized body, so the same key cannot silently become a different purchase. A unique database key backs up that identity.

    if ($previous) {
        if (!hash_equals($previous["body_hash"], $hash)) {
            throw new DomainException("Different request");
        }
        return $originalDecision;
    }

    Read the full tutorial step

    Example 03 · Tutorial excerpt

    Commit a complete decision or restore all of it

    Choose Failure before commit. The injected exception occurs after stock, order and outbox writes. The catch path rolls back the transaction before the exception leaves the service. The detail panel preserves the after-failure snapshot, then shows a retry. Without the transaction, stock can disappear without an order.

    $db->beginTransaction();
    try { /* inventory + order + outbox */ $db->commit(); }
    catch (Throwable $e) {
        if ($db->inTransaction()) $db->rollBack();
        throw $e;
    }

    Read the full tutorial step

    Example 04 · Tutorial excerpt

    Write the intent to deliver beside the order

    An outbox row records a committed intention to notify another system. It shares the order transaction. A later worker can find undelivered rows. The browser demo does not contact a service; it exercises a local receiver whose inbox uses the event key as a uniqueness boundary. Lost acknowledgments can cause redelivery even after useful work succeeded.

    INSERT INTO outbox (event_key, request_key) VALUES (?, ?);
    -- The receiving fixture records a unique event_key in inbox.

    Read the full tutorial step

    Example 05 · Tutorial excerpt

    Inspect the plan and preserve the answer

    The query exercise creates 5,000 invented history rows on every run. Without the matching index, inspect the scan and ordering work. With it, inspect the indexed lookup. The native regression compares result IDs before and after the index. Improving a plan while changing the answer is not an optimization of the same query.

    CREATE INDEX history_customer_status_recent
    ON quote_history(customer, status, created DESC);

    Read the full tutorial step