0Pricing
Firebase Auth & Realtime Database Apps · Aula

Operações transacionais de dados

Aprenda a usar transações para evitar condições de corrida e garantir atualizações atômicas em dados essenciais.

Operações transacionais de dados é uma aula grátis de Firebase Auth & Realtime Database Apps no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Firebase Auth & Realtime Database Apps, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Firebase Auth & Realtime Database Apps inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why Data Integrity Matters

In real-time applications, multiple users might try to update the same data simultaneously. This can lead to serious issues like data corruption or inconsistencies if not handled correctly.

Imagine a simple counter on a website. If two users click 'Like' at the exact same moment, the counter should increment by two, not just one.

The Race Condition Problem

Without proper synchronization, a common scenario called a race condition can occur. This happens when the outcome of an operation depends on the unpredictable sequence or timing of other operations.

For example, if you read a value, increment it, and then write it back, another user might read the original value before you write your incremented one, causing an update to be lost.

Introducing Firebase Transactions

Firebase Realtime Database provides a powerful feature called transactions to solve race conditions and ensure data integrity. A transaction guarantees an atomic update.

Atomic means the operation either completes entirely or doesn't happen at all. It's like a single, unbreakable step.

How `runTransaction` Works

You initiate a transaction using the runTransaction() method on a DatabaseReference. This method takes a Transaction.Handler callback.

  • Firebase passes the current state of the data to your handler.
  • You modify this data within the handler.
  • If another client writes to the same location while your transaction is running, Firebase automatically retries your transaction with the new current data.

Implementing a Safe Counter

Let's see how to safely increment a counter using a transaction. This ensures that even if multiple users try to increment simultaneously, the count will always be correct.

Try running this example:

public class Main {

  // Mock Firebase classes for demonstration
  static class MockFirebaseDatabase {
    private Integer value = 0; // Simulate data at a path
    public Integer get() { return value; }
    public void set(Integer val) { value = val; }

    public interface TransactionHandler {
      TransactionResult doTransaction(MutableData currentData);
    }

    public static class MutableData {
      private Integer data;
      public MutableData(Integer data) { this.data = data; }
      public Integer getValue() { return data; }
      public void setValue(Integer data) { this.data = data; }
    }

    public static class TransactionResult {
      private boolean success;
      private MutableData newData;
      private TransactionResult(boolean success, MutableData newData) {
        this.success = success;
        this.newData = newData;
      }
      public static TransactionResult success(MutableData newData) {
        return new TransactionResult(true, newData);
      }
      public static TransactionResult abort() {
        return new TransactionResult(false, null);
      }
      public boolean isSuccess() { return success; }
      public MutableData getNewData() { return newData; }
    }

    public void runTransaction(TransactionHandler handler) {
      // Simulate read, modify, and retry logic
      MutableData currentData = new MutableData(this.get());
      TransactionResult result = handler.doTransaction(currentData);

      if (result.isSuccess()) {
        this.set(result.getNewData().getValue());
        System.out.println("Transaction committed. New value: " + this.get());
      } else {
        System.out.println("Transaction aborted.");
      }
    }
  }

  public static void main(String[] args) {
    MockFirebaseDatabase counterRef = new MockFirebaseDatabase();
    counterRef.set(5); // Initial value

    counterRef.runTransaction(new MockFirebaseDatabase.TransactionHandler() {
      @Override
      public MockFirebaseDatabase.TransactionResult doTransaction(MockFirebaseDatabase.MutableData currentData) {
        Integer currentValue = currentData.getValue();
        if (currentValue == null) {
          currentValue = 0;
        }
        currentData.setValue(currentValue + 1);
        return MockFirebaseDatabase.TransactionResult.success(currentData);
      }
    });
  }
}

Understanding `MutableData`

Inside your Transaction.Handler, the MutableData object represents the data at the database location you're trying to modify.

  • Use currentData.getValue() to read the existing value.
  • Use currentData.setValue(newValue) to set the new value you want to write.

Remember, this is the data Firebase will try to commit. If a conflict occurs, your handler will be called again with the updated MutableData.

`TransactionResult` and Aborting

After processing the MutableData, your handler must return a Transaction.Result:

  • Transaction.Result.success(mutableData): Tells Firebase to try to commit the new value in mutableData.
  • Transaction.Result.abort(): Tells Firebase to cancel the transaction. This is useful if the data is in an unexpected state or if your logic determines the transaction shouldn't proceed.

Here's an example of aborting a transaction:

public class Main {

  // Mock Firebase classes (repeated for full program requirement)
  static class MockFirebaseDatabase {
    private Integer value = 0;
    public Integer get() { return value; }
    public void set(Integer val) { value = val; }

    public interface TransactionHandler {
      TransactionResult doTransaction(MutableData currentData);
    }

    public static class MutableData {
      private Integer data;
      public MutableData(Integer data) { this.data = data; }
      public Integer getValue() { return data; }
      public void setValue(Integer data) { this.data = data; }
    }

    public static class TransactionResult {
      private boolean success;
      private MutableData newData;
      private TransactionResult(boolean success, MutableData newData) {
        this.success = success;
        this.newData = newData;
      }
      public static TransactionResult success(MutableData newData) {
        return new TransactionResult(true, newData);
      }
      public static TransactionResult abort() {
        return new TransactionResult(false, null);
      }
      public boolean isSuccess() { return success; }
      public MutableData getNewData() { return newData; }
    }

    public void runTransaction(TransactionHandler handler) {
      MutableData currentData = new MutableData(this.get());
      TransactionResult result = handler.doTransaction(currentData);

      if (result.isSuccess()) {
        this.set(result.getNewData().getValue());
        System.out.println("Transaction committed. New value: " + this.get());
      } else {
        System.out.println("Transaction aborted.");
      }
    }
  }

  public static void main(String[] args) {
    MockFirebaseDatabase statusRef = new MockFirebaseDatabase();
    statusRef.set(1); // 1 = Active, 0 = Inactive

    // Try to change status, but abort if it's already Inactive (0)
    statusRef.runTransaction(new MockFirebaseDatabase.TransactionHandler() {
      @Override
      public MockFirebaseDatabase.TransactionResult doTransaction(MockFirebaseDatabase.MutableData currentData) {
        Integer status = currentData.getValue();
        if (status != null && status == 0) {
          System.out.println("Status is already Inactive. Aborting transaction.");
          return MockFirebaseDatabase.TransactionResult.abort();
        }
        // Change status to 0 (Inactive)
        currentData.setValue(0);
        return MockFirebaseDatabase.TransactionResult.success(currentData);
      }
    });
  }
}

Handling Transaction Completion

After calling runTransaction(), you'll typically want to know if it succeeded or failed. Firebase provides an onComplete callback for this.

This callback gives you:

  • error: If the transaction failed.
  • committed: A boolean indicating if the transaction was committed.
  • currentData: The final state of the data.

Use this callback to update your UI or handle any post-transaction logic.

Beyond Simple Counters

Transactions are invaluable for any scenario requiring strong data consistency:

  • Unique Usernames: Ensure a username is truly unique before assigning it.
  • Voting Systems: Prevent double-voting or ensure vote counts are accurate.
  • Inventory Management: Safely decrement stock levels without overselling.
  • Game Scores: Update high scores reliably in multiplayer games.

Quick Check

Transactions are crucial for maintaining data integrity in concurrent environments. Which of the following best describes the primary benefit of using Firebase Realtime Database transactions?

Recap & Next Steps

You've learned about the critical role of transactional data operations in maintaining data integrity in real-time applications.

  • We explored race conditions and why they're problematic.
  • You now understand how Firebase's runTransaction() method ensures atomic updates.
  • We saw examples of safely incrementing counters and using Transaction.Result.abort().

Transactions are a powerful tool, but use them judiciously as they can be slower than direct writes. In the next lesson, we'll dive into atomic counters and queues!

Perguntas Frequentes

A aula “Operações transacionais de dados” é grátis?

Sim — o texto completo de “Operações transacionais de dados” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Firebase Auth & Realtime Database Apps, atualize para CoddyKit PRO. O curso de Firebase Auth & Realtime Database Apps inclui 4 aulas no total.

O que vou aprender em “Operações transacionais de dados”?

Aprenda a usar transações para evitar condições de corrida e garantir atualizações atômicas em dados essenciais. Você pratica Firebase Auth & Realtime Database Apps com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Firebase Auth & Realtime Database Apps?

Nenhuma experiência prévia é necessária. Firebase Auth & Realtime Database Apps no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Operações transacionais de dados”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Firebase Auth & Realtime Database Apps?

Sim. Cada aula de Firebase Auth & Realtime Database Apps inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Atualizações de dados em cascata
  2. Operações transacionais de dados
  3. Contadores e filas atômicos
  4. Estratégias de Desnormalização e Duplicação de Dados
← Voltar para Firebase Auth & Realtime Database Apps