# Transactions Published articles for Transactions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite DevFeed: [How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite]() Original publisher: [Read original article]() Author: Hugo Teijiz Published: 2026-09-17T23:27:03Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Legacy Modernization](), [migration](), [Refactoring](), [Testing](), [Integration testing](), [observability](), [Routing (disambiguation)](), [Transactions](), [TypeScript](), [API](), [service](), [Dependency injection]() Tags: [artificial-intelligence](), [how-to](), [incremental](), [integration-testing](), [legacy](), [legacy-code](), [migrate](), [migration](), [monolith](), [refactoring](), [rewrite](), [routing](), [software-architecture](), [transactions]() ### AI overview A tutorial on migrating a legacy monolith incrementally by moving one business capability at a time. It covers characterization tests, boundaries between legacy and new code, parallel implementations, progressive traffic, observability, rollback paths, data ownership, and removing migrated behavior. ### Source excerpt Large legacy migrations often fail long before the final cutover. The failure usually starts when the migration is framed as a single event. Move the application. Move the database. Move all the users ## When the team plays, Pix pauses: what the World Cup teaches us about outliers DevFeed: [When the team plays, Pix pauses: what the World Cup teaches us about outliers]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-17T15:17:19Z Content type: article Language: en Sources: [Nubank]() Topics: [data](), [context](), [Transactions](), [Risk](), [reliability]() Tags: [ai-research](), [context](), [data](), [data-science-machine-learning](), [patterns](), [payment](), [transactions]() ### AI overview The article uses World Cup matches as an example of how coordinated changes in everyday behavior can create outliers in payment data. It explains that instant-transfer volume drops during a match, returns after the final whistle, and may show a halftime pattern, emphasizing that anomalies must be assessed against the normal rhythm of transactions and their context. ### Source excerpt How World Cup matches turn everyday payment patterns into outliers and what those anomalies can teach us about data, risk, and reliability The post When the team plays, Pix pauses: what the World Cup teaches us about outliers appeared first on Building Nubank. ## Introducing Lead: TIN-compatible full-text search for CI DevFeed: [Introducing Lead: TIN-compatible full-text search for CI]() Original publisher: [Read original article]() Author: Eric Ridge Published: 2026-09-17T00:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [ci](), [Development](), [Databases](), [SQL]() Tags: [3](), [acid](), [ansi](), [bm25](), [ci](), [concurrent](), [engineering](), [extension](), [full-text-search](), [html](), [lead](), [make](), [postgres](), [search](), [sql](), [staging](), [tests](), [tokenizers](), [transactions](), [version]() ### AI overview Lead is a TIN-compatible PostgreSQL full-text search extension designed for CI, development, and staging. It preserves TIN's search features and correctness but uses full table scans, making it much slower and suitable for small test datasets rather than production workloads. ### Source excerpt Lead is a feature-equivalent version of TIN you can run in CI ## The User Write Lock: an Alternative to Transactions for Google App Engine DevFeed: [The User Write Lock: an Alternative to Transactions for Google App Engine]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-06-20T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Transactions](), [Databases](), [Google]() Tags: [caching](), [databases](), [engineering](), [google](), [infrastructure](), [news](), [processes](), [retry](), [transactions]() ### AI overview This developer article explains how transactions in Google App Engine's datastore provide atomicity for single-entity and multi-entity writes, but can introduce frozen datastore state, retries, idempotence requirements, and restrictions on datastore queries. It presents the User Write Lock as an alternative, although the supplied text ends before describing that alternative. ### Source excerpt By Craig Silverstein Transactions are the standard method in Google App Engine's datastore -- as in many databases ... Read more ## Ensuring transaction-safety in Google App Engine DevFeed: [Ensuring transaction-safety in Google App Engine]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-06-27T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Transactions](), [Databases](), [Code](), [Google]() Tags: [cache](), [code](), [database](), [engineering](), [google](), [hooks](), [infrastructure](), [news](), [tracing](), [transactions]() ### AI overview The article explains how Khan Academy uses transactions and user-write locks with Google App Engine to prevent database corruption caused by concurrent requests overwriting one another. It describes hooks that detect transaction-safety violations and highlights caching and code-path mistakes that can cause stale data to be used inside transactions. ### Source excerpt By Craig Silverstein In last week's exciting post, I described an alternative to transactions that we use at ... Read more ## Troubleshooting row lock contention in Amazon Aurora PostgreSQL: Part 1 - Understanding row lock contention in PostgreSQL DevFeed: [Troubleshooting row lock contention in Amazon Aurora PostgreSQL: Part 1 - Understanding row lock contention in PostgreSQL]() Original publisher: [Read original article]() Author: Sameer Kumar Published: 2026-09-14T16:02:08Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon Aurora](), [PostgreSQL](), [Concurrency](), [Monitoring](), [Transactions](), [Amazon CloudWatch](), [Amazon RDS](), [Architecture & Design](), [Extension]() Tags: [advanced-300](), [amazon-aurora](), [amazon-cloudwatch](), [amazon-rds](), [architecture](), [availability](), [concurrency](), [database](), [database-performance](), [extension](), [locks](), [monitoring](), [postgresql](), [production](), [rds-for-postgresql](), [technical-how-to](), [transactions](), [troubleshooting]() ### AI overview This first part of a two-part series explains row lock contention in PostgreSQL and Amazon Aurora PostgreSQL. It covers how concurrent transactions competing for the same rows can reduce throughput and cause timeouts despite healthy CPU and I/O, then introduces PostgreSQL locking internals and monitoring techniques using system views, functions, the pgrowlocks extension, and log_lock_waits. The article notes that the same behavior and investigation approach apply to Amazon RDS for PostgreSQL. ### Source excerpt Row lock contention can collapse database throughput during a flash sale even when CPU and I/O look healthy. In Part 1 of this series, learn how PostgreSQL row locking works and how to monitor lock contention in Amazon Aurora PostgreSQL and Amazon RDS for PostgreSQL using system views, the pgrowlocks extension, and the log_lock_waits parameter. ## Solana: Building, Proving and Earning Trust in Public DevFeed: [Solana: Building, Proving and Earning Trust in Public]() Original publisher: [Read original article]() Author: Jacob Creech Published: 2026-09-14T11:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Network](), [Critical Infrastructure](), [incident](), [networking](), [Transactions](), [Amazon Web Services]() Tags: [2026](), [aws](), [blockchain](), [blockchain-technology](), [building](), [critical-infrastructure](), [crypto](), [crypto-news](), [cryptocurrency](), [defi](), [ecosystem](), [incident](), [infrastructure](), [network](), [nfts](), [outages](), [podcasts](), [routing](), [solana](), [solana-ecosystem](), [technology](), [transactions](), [uptime](), [web3]() ### AI overview Solana describes how repeated public testing, transparent incident reporting, and corrective engineering have strengthened trust in the network. It highlights a 2026 routing failure that took nearly 29% of network stake offline while blocks and transactions continued, followed by recovery of the infrastructure provider in just over 30 minutes. The article also cites validator capacity improvements, stake-weighted quality of service, and a redesigned transaction scheduler as examples of resilience work. ### Source excerpt Solana has maintained 100% uptime since February 2024, including when a routing failure took nearly 29% of network stake offline. ## How to Prevent Race Conditions in Django DevFeed: [How to Prevent Race Conditions in Django]() Original publisher: [Read original article]() Author: Mari Published: 2026-09-11T21:50:46Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Concurrency](), [Database](), [SQLite](), [Docker]() Tags: [backend](), [concurrency](), [database](), [django](), [how-to](), [postgresql](), [python](), [race-condition](), [sqlite](), [transactions]() ### AI overview A Django tutorial that demonstrates a credit-spending race condition and explains how database transactions and row locks prevent concurrent requests from using the same credit. ### Source excerpt Let's say you have enough credit left to generate one more image in an AI app. You submit a request in one browser tab, then submit another in a second tab before the first finishes. The app accepts b ## Android malware creates a hidden copy of your banking app DevFeed: [Android malware creates a hidden copy of your banking app]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-11T12:14:55Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Malware](), [App]() Tags: [android](), [app](), [credential-theft](), [fraud](), [malware](), [mobile](), [news](), [phishing](), [profile](), [security](), [transactions]() ### AI overview Gigabud is an Android banking Trojan that creates a work profile and clones a banking app so operators can conduct fraudulent transactions separately from malware detected in the personal profile. ### Source excerpt The Gigabud banking Trojan can clone a banking app into a separate work profile on an Android device to help hide fraudulent transactions. ## Introducing WalShadow: Sub-second Postgres replication to ClickHouse from physical WAL DevFeed: [Introducing WalShadow: Sub-second Postgres replication to ClickHouse from physical WAL]() Original publisher: [Read original article]() Author: Sai Srirampur Published: 2026-09-10T15:53:42Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Database](), [schema-evolution](), [Latency]() Tags: [analytics](), [architecture](), [benchmarks](), [clickhouse](), [github](), [latency](), [open-source](), [postgres](), [replication](), [schema-evolution](), [transactions]() ### AI overview WalShadow is an open-source engine that replicates PostgreSQL data to ClickHouse from the physical WAL stream. The article describes benchmark results of about 200 ms visibility latency and 289K rows per second, plus support for initial loads, continuous replication, schema evolution, recovery, and source switchovers. ### Source excerpt WalShadow replicates Postgres data directly from physical WAL into ClickHouse, delivering around 200 ms latency and 289,000 rows per second in benchmarks. ## Thursday Notes on Architecture Trade-offs and High-Performing Teams DevFeed: [Thursday Notes on Architecture Trade-offs and High-Performing Teams]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-09-10T15:00:57Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [Architecture & Design](), [Microservice]() Tags: [architecture](), [fault-tolerance](), [security](), [software-architecture](), [split](), [team-topologies](), [transactions]() ### AI overview This issue of Thursday Notes discusses architecture as a search for acceptable trade-offs, including reasons to split or merge services. It also explains how teams cycle through forming, storming, norming, and performing, and how leadership should adapt to each stage. ### Source excerpt Hey, Milan here. ## Solana Ecosystem Roundup: August 2026 DevFeed: [Solana Ecosystem Roundup: August 2026]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-09-04T04:18:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Solana ecosystem](), [Transactions](), [DeFi](), [API]() Tags: [2026](), [api](), [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [ecosystem](), [finance](), [iphone](), [nfts](), [podcasts](), [solana](), [solana-ecosystem](), [stablecoins](), [transactions](), [web3]() ### AI overview Solana's August 2026 roundup reports record network activity, growth in real-world assets and tokenized stocks, expanding stablecoin payment infrastructure, ETF inflows, and broader consumer-app distribution. ### Source excerpt Solana's August 2026 roundup: record transactions, $4B in RWAs, growing stablecoin payments, tokenized stocks, DeFi innovation, ETFs, and governance. ## Keyboard Navigation and Data Entry DevFeed: [Keyboard Navigation and Data Entry]() Original publisher: [Read original article]() Author: William Hudson Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [UX Daily - User Experience Daily]() Topics: [User interface design](), [Accessibility](), [data]() Tags: [accessibility](), [amazon](), [compliance](), [design](), [forms](), [transactions](), [usability](), [visual-hierarchy]() ### AI overview This article explains how keyboard navigation, clear action hierarchy, flexible data entry, and review steps improve the usability and accessibility of forms. It covers tab order, assistive technology users, minimizing keyboard-mouse switching, and WCAG guidance for important transactions. ### Source excerpt Forms are an essential part of many interactions, but good form layout and clear labels are only part of the picture. Forms also need to work in all the ways users interact with them. Not everyone uses a mouse. Many users rely on keyboards, whether by preference, motor impairments, or because they use assistive technologies such as screen readers. How a form handles keyboard navigation, action buttons, and data entry has a direct impact on both usability and accessibility compliance.In the video, William Hudson explores the interaction side of form design: how users move through forms, how primary and secondary actions should be distinguished, and why flexible input handling is one of the si... ## Payment Channels: 1 Million Payments Per Second DevFeed: [Payment Channels: 1 Million Payments Per Second]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-09-03T16:26:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [Artificial Intelligence]() Tags: [agent](), [agentic](), [agents](), [ai](), [announcements](), [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [nfts](), [payment](), [payments](), [podcasts](), [product](), [solana](), [solana-ecosystem](), [streaming](), [transactions](), [web3]() ### AI overview This article explains how Solana payment channels support agentic payments by authorizing a spending limit once, metering usage through signed off-chain messages, and settling the consumed amount in a single on-chain transaction. ### Source excerpt Payment channels support 1 million payments per second by authorizing agent spending once. ## Announcing DocumentsDB: Documents that evolve with your product DevFeed: [Announcing DocumentsDB: Documents that evolve with your product]() Original publisher: [Read original article]() Author: Arnab Chatterjee Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Databases](), [GeoJSON](), [SDKs]() Tags: [announcements](), [database](), [json](), [product](), [products](), [scheduled](), [sdk](), [snapshots](), [transactions]() ### AI overview Appwrite announces DocumentsDB, a schemaless database for flexible JSON documents whose fields can evolve without defining columns or running schema migrations. It supports Appwrite SDK patterns and database capabilities such as permissions, queries, transactions, bulk operations, imports, exports, and backups. ### Source excerpt Store flexible JSON documents, query them with the Appwrite SDKs, and let your data model evolve with your product instead of ahead of it. ## Native databases vs Appwrite databases: which one should you pick? DevFeed: [Native databases vs Appwrite databases: which one should you pick?]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Databases](), [MySQL](), [PostgreSQL](), [SDKs]() Tags: [api](), [backend](), [comparisons](), [databases](), [guide](), [mysql](), [orm](), [postgresql](), [realtime](), [transactions]() ### AI overview This guide compares Appwrite's managed TablesDB, DocumentsDB, and VectorsDB with native PostgreSQL and MySQL databases. It explains the trade-off between Appwrite's SDK-based permissions, realtime events, functions, and other platform features and the direct SQL access available through native database drivers or ORMs. ### Source excerpt Appwrite offers two kinds of databases. This guide explains how TablesDB, DocumentsDB, and VectorsDB differ from native PostgreSQL and MySQL, and how to choose between them for your project. ## The invisible heartbeat of our networks DevFeed: [The invisible heartbeat of our networks]() Original publisher: [Read original article]() Author: Luca Cicchelli Published: 2026-08-31T23:03:47Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Networks](), [distributed-systems](), [Critical Infrastructure](), [Security](), [5G](), [Cybersecurity](), [cloud-infrastructure](), [AI Infrastructure]() Tags: [5g](), [ai](), [ai-infrastructure](), [critical-infrastructure](), [cybersecurity](), [data](), [distributed-systems](), [engineering](), [gnss](), [gps](), [guest-post](), [hardware](), [network](), [networking](), [networks](), [outage](), [outages](), [post](), [servers](), [systems](), [tech-matters](), [time](), [transactions]() ### AI overview The article examines how accurate time synchronization underpins modern networks and distributed systems. It uses the Telstra outage to show how misaligned time servers can disrupt communications and rail services, and discusses resilient time sources, terrestrial backups, local atomic clocks, and synchronization requirements for finance, 5G, cloud, and AI infrastructure. ### Source excerpt Guest Post: The recent Telstra outage highlighted a critical but often overlooked dependency in modern networks: Accurate time synchronization. ## How one connection kills a database DevFeed: [How one connection kills a database]() Original publisher: [Read original article]() Author: Simeon Griggs Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [debugging](), [migration](), [dashboards](), [vitess]() Tags: [app](), [cli](), [database](), [debugging](), [errors](), [exception](), [github](), [management](), [migration](), [mysql](), [postgres](), [product](), [transactions](), [vitess]() ### AI overview The article explains how an unclosed database transaction can block a migration and queue later queries, causing downtime. It discusses diagnosing live MySQL and Postgres connections and preventing stuck Postgres transactions with a timeout. ### Source excerpt Unblock stuck connections with live connection management in the PlanetScale CLI and dashboard ## Solana Changelog: August 27, 2026 DevFeed: [Solana Changelog: August 27, 2026]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-08-28T16:00:00Z Content type: release Language: en Sources: [Solana News Feed]() Topics: [changelog](), [Solana](), [releases](), [Tooling](), [SDKs](), [Transactions](), [Network]() Tags: [2026](), [announcements](), [blockchain](), [blockchain-technology](), [changelog](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [javascript](), [network](), [newsletter](), [nfts](), [podcasts](), [release](), [releases](), [sdk](), [sdks](), [solana](), [solana-ecosystem](), [technology](), [tooling](), [transactions](), [v5](), [web3]() ### AI overview The August 27, 2026 Solana changelog covers approaching V1 Transactions, a Mainnet feature gate reducing slot time to 300ms, releases across Solana tooling and SDKs, and proposed protocol changes. ### Source excerpt V1 Transactions are approaching, while a 300ms slot-time feature gate reached Mainnet and new releases shipped across Solana tooling. ## Concurrent Writes in Practice: Building High-Throughput Apps with Turso's MVCC DevFeed: [Concurrent Writes in Practice: Building High-Throughput Apps with Turso's MVCC]() Original publisher: [Read original article]() Author: Jeff Olson Published: 2026-08-27T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [backends](), [cpu]() Tags: [benchmarks](), [cpu](), [database](), [performance](), [python](), [rust](), [sqlite](), [transactions](), [turso](), [typescript]() ### AI overview A practical guide to using Turso's concurrent-write capability for high-throughput SQLite applications. It explains contention from SQLite's single-writer model and discusses transaction conflicts, retries, and workloads that include computation. ### Source excerpt What it looks like to actually build with BEGIN CONCURRENT: when to reach for it, working code in TypeScript, Python, and Rust, and how to handle conflicts. ## Introducing Neon Labs DevFeed: [Introducing Neon Labs]() Original publisher: [Read original article]() Author: Savannah Longoria Published: 2026-08-26T12:00:00Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [migration](), [Databases](), [Replication](), [Transactions](), [Availability]() Tags: [agent](), [availability](), [database](), [migration](), [playground](), [postgres](), [product](), [replication](), [tools](), [transactions]() ### AI overview Neon Labs is a new home for experimental tools built around Lakebase Postgres. Its first release includes a Postgres Upgrade Assessment that identifies version-upgrade blockers and a Migration Assistant that recommends a migration method. The tools are intended for development or testing while they remain experimental. ### Source excerpt Today we're launching Neon Labs, a home for experimental tools built around Lakebase Postgres. We want Neon Labs to be a playground for ideas that could help the broader Postgres community. ## Postgres + ClickHouse Architectural Patterns DevFeed: [Postgres + ClickHouse Architectural Patterns]() Original publisher: [Read original article]() Author: Agus Syafaat Published: 2026-08-26T08:08:43Z Content type: article Language: en Sources: [SeveralNines]() Topics: [clickhouse](), [PostgreSQL](), [Databases](), [Architecture & Design](), [data-platforms](), [real-time](), [Transactions](), [Low Latency](), [dashboards]() Tags: [analytics](), [architecture](), [clickhouse](), [clustercontrol](), [database-general](), [hybrid-operations](), [latency](), [olap](), [postgres](), [postgresql](), [real-time](), [time](), [transactions]() ### AI overview This article explains architectural patterns that combine PostgreSQL and ClickHouse. PostgreSQL serves as the authoritative transactional system for OLTP workloads, while ClickHouse handles large-scale analytical queries and real-time analytics. Continuous Change Data Capture synchronization connects the systems and separates transactional and analytical workloads. ### Source excerpt The role of databases has shifted significantly as modern applications must deliver real-time analytics, dashboards, and machine learning alongside low-latency transaction processing. Handling these diverse demands with a single relational database has become unsustainable under growing data volumes. Consequently, organizations are adopting specialized database architectures where multiple engines work together based on their strengths, allowing [...] The post Postgres + ClickHouse Architectural Patterns appeared first on Severalnines. ## State divergence enables unauthorized access DevFeed: [State divergence enables unauthorized access]() Original publisher: [Read original article]() Author: "Paweł Płatek"; "Denys Pakizh" Published: 2026-08-25T11:00:00Z Content type: article Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [bug](), [Blockchain](), [Authorization](), [Transactions](), [SDKs]() Tags: [2026](), [access-control](), [audits](), [authorization](), [blockchain](), [bug](), [financial-services](), [module](), [tokens](), [transactions](), [vulnerabilities]() ### AI overview The article describes a Provenance Blockchain authorization bug that allowed users to grant themselves admin control over marker accounts without holding tokens. The flaw affected non-fixed-supply markers because the access check read a stale zero-valued supply field instead of the live circulating supply. The issue was mitigated in v1.28.0 and fixed in v1.29.0. ### Source excerpt We found and reported a bug in Provenance Blockchain, a public proof-of-stake chain built on Cosmos SDK, that lets any user grant themselves admin control over marker accounts without holding a single token. Provenance covers a range of financial services, including on-chain tokenized loans, private equity tokens, bridged assets, and asset registries. Our bug affected 82 markers representing live financial assets on mainnet. We found the bug, which affects versions before 1.28.0, in March 2026, and reported it to Provenance on April 1. It was mitigated in PR #2627 (commit c81fd65), which shipped in v1.28.0 on May 1, 2026, and fixed in PR #2734, which shipped in v1.29.0 on June 8, 2026. What is a marker? The marker module is Provenance's core primitive for fungible tokens. Chain participants can issue a new asset on Provenance by submitting a MsgAddMarkerRequest transaction; the chain creates a dedicated account for that asset, called a marker. Each marker is a special account type that controls: A denomination (e.g., uusd.trading, cusd.deposit, cguaranteedrateomni) An access control list governing who can mint, burn, withdraw, deposit, or administer the token A supply field recording the canonical token count An escrow balance (the marker account can hold any asset, not just its own denomination) Markers are either supply_fixed (the supply field is enforced as a hard cap) or non-fixed (the bank module is the source of truth; the supply field is informational). This distinction is central to the bug. The bug: An access check anyone can pass AddAccess is the Cosmos SDK message handler that processes requests to modify a marker's access control list. It checks whether the caller is authorized using three conditions, any one of which is sufficient: The caller is the marker's designated manager and the marker is in Finalized state. The caller already holds ACCESS_ADMIN on the marker. The caller controls 100% of the marker's circulating supply. case types.StatusFinalized, ## WAL + S3: Lakebase storage for the era of agents DevFeed: [WAL + S3: Lakebase storage for the era of agents]() Original publisher: [Read original article]() Author: Carlota Soto Published: 2026-08-24T12:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [Amazon S3](), [Transactions](), [data](), [migration]() Tags: [agents](), [data](), [database](), [engineering](), [migration](), [product](), [s3](), [storage](), [transactions]() ### AI overview The article argues that PostgreSQL workloads associated with agents need storage built around transaction history rather than only the current state. It presents the write-ahead log as an existing timeline of database modifications and examines placing S3 beneath PostgreSQL to support isolated copies, point-in-time restoration, historical queries, and many disposable environments more efficiently. ### Source excerpt Agents treat code as lightweight: branch it, deploy it, throw it away. The infrastructure under that code should work the same way. Working with an OLTP database is traditionally heavy and full of friction, but very little of that is a Postgres problem. [Next page]()