Node-Boot Framework
  • πŸ‘‹Welcome to Node-Boot
  • πŸ’‘Why Node-Boot?
    • No CLI
    • No Boilerplate
    • Standardisation at its core
    • Spring-Boot Features Parity
  • πŸ₯‡Mission
  • πŸš€Getting Started
  • Letter to Developers
    • πŸ“Letter to Node.Js Developers
    • πŸ“Letter to Web3 Developers
    • πŸ“Letter to Spring-Boot Developers
    • πŸ“Letter to Node.Js Framework Developers
  • Fundamentals
    • 🧩Architecture
      • Overview
      • Bootstrap
      • Lifecycle
      • Application Context
    • πŸͺ„Core Features
      • Dependency Injection
      • Bean and Configuration
      • Configuration Properties
        • Static Configuration
        • Reading Configuration
        • Writing Configuration
        • Defining Configuration
        • Configuration Properties
      • Controller
        • Available Decorators
        • Custom Decorator
        • Versioning
      • Service
      • Component
      • Logging
      • Error Handling
      • Transactions
        • Transaction Principles
        • Transactions vs Concurrency
        • πŸ™ˆUsing Transactions
      • Middleware/Interceptors
      • Authorization
      • Marshalling vs Unmarshalling
    • πŸ—οΈAuto-Configuration
    • πŸ”Security
  • Servers
    • πŸš‚Servers Concept
    • πŸšƒAvailable Servers
      • Fastify
      • Express
      • Koa
    • πŸ”ŒIntegrate Server?
  • Starters
    • πŸ—οΈStarters Overview
    • 🎁Available Starters
      • Persistency
      • Validations
      • Actuator
      • Open API
      • Redis
Powered by GitBook
On this page
  1. Fundamentals
  2. Core Features
  3. Transactions

Transaction Principles

Key Concepts of Transactions

A.C.I.D is an acronym that refers to the set of 4 key properties that define a transaction: Atomicity, Consistency, Isolation, and Durability. If a database operation has these A.C.I.D properties, it can be called an A.C.I.D transaction, and data storage systems that apply these operations are called transactional systems. A.C.I.D transactions guarantee that each read, write, or modification of a table has the following properties:

Atomicity

Atomicity guarantees that each transaction is treated as a single "atomic" unit. It either completes in its entirety or has no effect at all. This is essential for maintaining data integrity, as it prevents partial updates that could lead to inconsistent states.

Consistency

Consistency ensures that a transaction brings the database from one valid state to another. The database's rules, such as constraints, cascades, and triggers, are preserved.

Isolation

Isolation ensures that transactions are executed in isolation from one another. Concurrent transactions should not affect each other, providing a predictable outcome as if the transactions were executed sequentially.

Durability

Durability guarantees that once a transaction has been committed, it remains in the system even in the event of a system failure. This ensures the permanence of the transaction’s outcome.

PreviousTransactionsNextTransactions vs Concurrency

Last updated 1 year ago

πŸͺ„