# Transactions Database transactions are logical units of work that group operations into all-or-nothing execution and provide ACID guarantees such as consistency, isolation, and durability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Too many GCache Page Files in MySQL Data Directory DevFeed: [Too many GCache Page Files in MySQL Data Directory]() Original publisher: [Read original article]() Author: Kedar Vaijanapurkar Published: 2026-09-17T05:29:14Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [XtraDB Cluster (PXC)](), [Replication](), [Transactions](), [MySQL]() Tags: [cluster](), [database-administration](), [disk-space](), [galera](), [galera-replication](), [gcache](), [gcache-freeze-purge-at-seqno](), [gcache-keep-pages-count](), [gcache-page](), [gcache-page-files](), [gcache-purge](), [gcache-troubleshooting](), [mysql](), [mysql-disk-space](), [mysql-troubleshooting](), [percona-xtradb-cluster](), [pxc](), [replication](), [xtradb-cluster-pxc]() ### AI overview An investigation into thousands of GCache page files accumulating in a Percona XtraDB Cluster data directory. The article explains how frozen GCache purging caused disk growth, links the behavior to a cluster partition, and describes reproducing it by setting gcache.freeze_purge_at_seqno and generating workload. ### Source excerpt Learn why PXC accumulates thousands of gcache.page.* files, how frozen GCache purging causes disk growth, and how to safely recover and rejoin using IST. The post Too many GCache Page Files in MySQL Data Directory appeared first on Percona. ## 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 ## What is Trust and Safety? DevFeed: [What is Trust and Safety?]() Original publisher: [Read original article]() Author: Ben Price Published: 2026-08-28T23:00:00Z Content type: article Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Transactions](), [account takeover]() Tags: [account-takeover](), [authentication](), [chargebacks](), [digital-platforms](), [digital-trust](), [digital-trust-safety](), [fraud-detection](), [fraud-prevention](), [payment-fraud](), [trust](), [trust-and-safety](), [trust-safety]() ### AI overview This article explains Trust and Safety as an organizational capability for protecting digital platforms, users, transactions, and interactions. It describes how the discipline brings together fraud prevention, content moderation, abuse prevention, and policy enforcement across the user journey, including payment fraud, fake account creation, account takeover, and content integrity. ### Source excerpt Trust and Safety is the practice of protecting the integrity of digital platforms, their users, and the transactions and interactions that take place on them. As a discipline, trust and safety spans fraud prevention, content moderation, abuse prevention, and policy enforcement across the full user journey. For fraud teams and platform operators, it represents a [...] The post What is Trust and Safety? appeared first on Sift. ## 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. ## 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. ## 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. ## Recurly vs Stripe: Billing Layer Costs Compared for 2026 DevFeed: [Recurly vs Stripe: Billing Layer Costs Compared for 2026]() Original publisher: [Read original article]() Author: Deepak Jangir Published: 2026-08-30T00:00:00Z Content type: comparison Language: en Sources: [Dodo Payments Blog]() Topics: [stripe](), [Transactions](), [Shopify]() Tags: [billing](), [comparison](), [payment](), [payments](), [pricing](), [saas](), [subscriptions](), [usage-based-billing]() ### AI overview A comparison of Recurly and Stripe Billing as competing subscription billing layers, covering published 2026 pricing, included features, payment processing costs, and the billing volumes at which each option becomes cheaper. ### Source excerpt Recurly vs Stripe for subscriptions: compare Recurly's $249 + 0.9% against Stripe Billing's 0.7%, find the crossover volumes, and see what neither one covers. ## 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. ## 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. ## Glamsterdam Repricing Impact for Smart Contract Developers DevFeed: [Glamsterdam Repricing Impact for Smart Contract Developers]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Research; EthPandaOps; and Specifications teams Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Solidity](), [Transactions]() Tags: [developers](), [ethereum](), [research-development](), [smart-contract](), [test](), [upgrade]() ### AI overview The upcoming Glamsterdam upgrade will reprice Ethereum state creation and access through EIP-8037 and EIP-8038. Historical transaction replays found that most contracts are unaffected, while some may require preventative updates or higher gas limits. ### Source excerpt ... ## Core Banking Modernization with Temenos Core and CockroachDB DevFeed: [Core Banking Modernization with Temenos Core and CockroachDB]() Original publisher: [Read original article]() Author: Nanda Badrappan,Muruga Balakrishnan Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Cockroach Labs](), [Data Infrastructure](), [Availability](), [real-time](), [Resilience](), [Transactions](), [legacy](), [SQL](), [Cloud](), [systems](), [on-prem]() Tags: [availability](), [cloud](), [cockroach-labs](), [cockroachdb](), [data-infrastructure](), [legacy](), [on-prem](), [real-time](), [resilience](), [sql](), [transactions]() ### AI overview This article explains why banks are modernizing legacy core banking infrastructure. It describes how Temenos Core and CockroachDB are positioned to support real-time transaction processing, continuous availability, distributed operations, resilience, and regulatory requirements. ### Source excerpt Banking has become an always-on business. Customers expect instant payments, accurate balances, and continuous access to financial services... ## Resource and Inclusion Fee: Digging into Data DevFeed: [Resource and Inclusion Fee: Digging into Data]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-21T15:34:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [Optimization](), [data]() Tags: [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [data](), [defi](), [nfts](), [optimization](), [podcasts](), [pricing](), [reports](), [solana](), [solana-ecosystem](), [transactions](), [upgrades](), [web3]() ### AI overview This article analyzes SGP-0003's proposed resource-aware base fee for Solana. It examines resource-request calibration, transaction fee effects across workloads, validator economics, and estimated SOL-burn changes, emphasizing that the burn figures are behavioral counterfactuals rather than forecasts. ### Source excerpt Here we dive into implications related to the SGP-0003 (namely resource and inclusion fee). ## Why global workers are driving demand for stablecoin payouts DevFeed: [Why global workers are driving demand for stablecoin payouts]() Original publisher: [Read original article]() Author: Siddharth Kulkarni; Mitchell Martins-Collum Published: 2026-08-19T00:00:00Z Content type: article Language: en Sources: [Stripe Blog]() Topics: [stripe](), [Transactions](), [Meta]() Tags: [cost](), [cross-border](), [fees](), [global](), [payments](), [speed](), [stripe](), [transactions]() ### AI overview This article examines why global gig workers, contractors, creators, freelancers, and marketplace sellers are increasingly interested in stablecoin payouts. Drawing on a Stripe survey of more than 2,300 workers across 20 countries, it highlights dissatisfaction with the fees and slow settlement of traditional cross-border payments, as well as demand for inflation protection, financial access, remittance relief, rewards on balances, education, and simpler wallet setup. ### Source excerpt Platforms like DoorDash, Meta, and Deel already enable stablecoin payouts for global workers. We surveyed 2,300 workers in 20 countries to see what's driving stablecoin demand, where the opportunity is highest, and how other platforms can adapt. ## New in Confluent Cloud and WarpStream: Evolving the Data Streaming Platform for AI, Scale, and Control DevFeed: [New in Confluent Cloud and WarpStream: Evolving the Data Streaming Platform for AI, Scale, and Control]() Original publisher: [Read original article]() Author: Mike Agnich Published: 2026-08-18T14:00:11Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Streaming](), [Kafka](), [Cloud](), [event driven](), [Transactions]() Tags: [confluent](), [confluent-cloud](), [debug](), [kafka](), [networking](), [security](), [stream-processing](), [streaming](), [transactions]() ### AI overview Confluent describes more than 70 new features for its data streaming platform, including new connectors, networking improvements, AI capabilities for event-driven agents, real-time machine learning in streaming pipelines, and AI-assisted development tools. The article also discusses broader Kafka workload support, including stream processing, transactions, exactly-once processing, queues, debugging, and Python client support for Queues for Kafka. ### Source excerpt Accelerate enterprise streaming and AI workloads with new product updates across Kora, connectors, Flink, Tableflow, AI anomaly detection and forecasting, security enhancements, and Warpstream. ## Agentic treasury runs on searchable, observable context DevFeed: [Agentic treasury runs on searchable, observable context]() Original publisher: [Read original article]() Author: Karen Mcdermott Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [Artificial Intelligence](), [observability](), [data](), [Latency](), [dashboards](), [Transactions](), [systems]() Tags: [agentic](), [agentic-ai](), [ai](), [banking](), [dashboards](), [data](), [elasticsearch-logs-metrics](), [erp](), [finance](), [financial-services](), [geospatial-log-analytics-metrics](), [latency](), [observability](), [payment](), [systems](), [transactions]() ### AI overview This article argues that agentic treasury depends on searchable context, observable systems, and trustworthy data rather than AI alone. It explains that treasury teams face decision latency because balances, transactions, forecasts, payment activity, liquidity positions, counterparty information, and market signals are fragmented across enterprise systems, platforms, dashboards, reports, and spreadsheets. ### Source excerpt Agentic treasury requires more than AI. It needs searchable context, observable systems, and trusted data to reduce decision latency and support confident, governed action. ## v1 Transactions and the ALT Trade-off DevFeed: [v1 Transactions and the ALT Trade-off]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [benchmarking](), [SDKs]() Tags: [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [nfts](), [podcasts](), [reference](), [reports](), [rpc](), [sdks](), [serialization](), [solana](), [solana-ecosystem](), [transactions](), [upgrades](), [web3]() ### AI overview Solana is introducing the v1 transaction format with a maximum serialized size of 4,096 bytes, replacing Account Lookup Table resolution with larger inline transaction capacity. The analysis finds that current workloads are broadly compatible with the new envelope, while the unchanged 64-account limit may remain a constraint for some applications. ### Source excerpt Solana is introducing a new transaction format (v1) alongside an increase of the maximum transaction size from 1232 bytes to 4096 bytes. The v1 format aims to unlock new possibilities on-chain. This is done trading-off Account Lookup Tables (ALT) usage. In this research we explore in details the current usage of ALTs, alongside implications of removing them. ## Buy Me a Coffee Alternatives: 5 Options for Creators Who Outgrew the Tip Jar DevFeed: [Buy Me a Coffee Alternatives: 5 Options for Creators Who Outgrew the Tip Jar]() Original publisher: [Read original article]() Author: Deepak Jangir Published: 2026-08-15T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Transactions](), [stripe]() Tags: [alternatives](), [comparison](), [creators](), [digital-products](), [fees](), [global](), [payment-processing](), [payments](), [stripe](), [tax](), [transactions]() ### AI overview A comparison of five Buy Me a Coffee alternatives for creators, focusing on stacked transaction fees, international tax obligations, memberships, and digital products. ### Source excerpt Compare Buy Me a Coffee alternatives with the real stacked fee math, the global tax liability gap most creators miss, and which platform fits memberships and digital products. ## Go SDK для YDB: уменьшаем количество запросов к СУБД для интерактивных транзакций DevFeed: [Go SDK для YDB: уменьшаем количество запросов к СУБД для интерактивных транзакций]() Original publisher: [Read original article]() Author: spesternikov (Яндекс, Yandex Cloud & Yandex Infrastructure, YDB) Published: 2026-08-13T13:23:34Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Go](), [SDKs](), [Transactions](), [Remote Procedure Call (RPC)]() Tags: [go](), [rpc](), [sdk](), [tag-8288660a1e40](), [tag-89f0c6f39f5d](), [tag-d4be1d74f775](), [transactions](), [ydb]() ### AI overview This Russian-language technical article explains how Yandex's YDB Go SDK reduces network round-trips for interactive transactions. It describes combining transaction startup with the first query through Lazy Transactions and notes that the improvements were included in Go SDK releases v3.126.0 and v3.126.5. ### Source excerpt Привет, Хабр! Меня зовут Степан Пестерников, мы с командой делаем Алису и активно используем СУБД Яндекса. Недавно коллеги из YDB провели большой рефакторинг в YDB Go SDK, где по умолчанию теперь используется новый Query Service. Я воспользовался этим рефакторингом, чтобы уменьшить количество сетевых запросов от SDK к YDB. Клиентские SDK устанавливают к распределённой СУБД Яндекса gRPC-подключения, поверх которых отправляются низкоуровневые команды. Какие-то из этих команд можно объединять: например, команду начала транзакции и выполнения первого запроса. В статье я покажу фрагменты кода и расскажу, как мы делали улучшения, которые вошли в релизы v3.126.0 и v3.126.5 Go SDK. Фрагменты кода получились небольшие, и на их примере удобно показать, как этими оптимизациями пользоваться. Читать далее ## DORA Compliance for AI Agents: Database Requirements Before Deployment DevFeed: [DORA Compliance for AI Agents: Database Requirements Before Deployment]() Original publisher: [Read original article]() Author: Quentin Packard Published: 2026-08-07T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [Databases](), [Artificial Intelligence](), [Resilience](), [audit](), [consistency](), [integrity](), [Transactions]() Tags: [ai-agents](), [audit](), [compliance](), [consistency](), [database](), [eu](), [gdpr](), [integrity](), [resilience](), [transactions]() ### AI overview This article explains database capabilities needed by financial AI agents operating under DORA, the EU AI Act, and GDPR. It focuses on auditability, agent identity attribution, strong read consistency, idempotency, rollback and compensating transactions, and data residency. It argues that these database properties help organizations demonstrate operational resilience, traceability, and transaction integrity before deployment. ### Source excerpt Financial AI agents operating under DORA, the EU AI Act, and GDPR need infrastructure that supports operational resilience, traceability, and reliable transaction processing. [Next page]()