# copy

Copy (data) is the replication of data in another location while retaining it in its original location.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## From Months to Days: How Autodesk Reinvented Its Data Ingestion Strategy | Blog | Fivetran

DevFeed: [From Months to Days: How Autodesk Reinvented Its Data Ingestion Strategy | Blog | Fivetran](<https://devfeed.tech/articles/from-months-to-days-how-autodesk-reinvented-its-data-ingestion-strategy-blog-fivetran-141321.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/how-autodesk-reinvented-its-data-ingestion-strategy>)

Author: Fivetran

Published: 2026-11-18T06:13:15Z

Content type: article

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [elt](<https://devfeed.tech/topics/elt.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [autodesk](<https://devfeed.tech/tags/autodesk.md>), [aws](<https://devfeed.tech/tags/aws.md>), [data](<https://devfeed.tech/tags/data.md>), [data-ingestion](<https://devfeed.tech/tags/data-ingestion.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [data-platform](<https://devfeed.tech/tags/data-platform.md>), [data-stack](<https://devfeed.tech/tags/data-stack.md>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [join](<https://devfeed.tech/tags/join.md>), [keep](<https://devfeed.tech/tags/keep.md>), [kinesis](<https://devfeed.tech/tags/kinesis.md>), [learning](<https://devfeed.tech/tags/learning.md>), [looker](<https://devfeed.tech/tags/looker.md>), [process](<https://devfeed.tech/tags/process.md>), [strategy](<https://devfeed.tech/tags/strategy.md>)

### AI overview

Autodesk replaced a patchwork of ingestion tools and custom scripts with two defined routes: Fivetran ingests structured sources into Snowflake, while AWS Kinesis sends high-volume unstructured product usage data to S3. Data moves between the repositories when needed; usage data can be promoted to Snowflake for analytics subject to privacy controls, and Snowflake snapshots are stored in S3 for history and machine learning. Autodesk's stated goal was to cut onboarding a dataset, including requirements, vendor setup, and security and privacy controls, from six months to six business days. The change reportedly freed engineers to focus on business problems and reduced urgent pipeline-breakage emails. The account attributes the approach to Autodesk's buy-over-build, simplicity, speed-to-impact, and privacy principles.

### Source excerpt

By replacing homemade ETL with automated ELT, Autodesk cut its data ingestion process from six months to six days.

## How we migrate TBs from Heroku without logical replication

DevFeed: [How we migrate TBs from Heroku without logical replication](<https://devfeed.tech/articles/how-we-migrate-tbs-from-heroku-without-logical-replication-130264.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/migrate-from-heroku-to-planetscale>)

Author: Dmitrii Anisovich

Published: 2026-11-11T00:00:00Z

Content type: tutorial

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [downtime](<https://devfeed.tech/tags/downtime.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [replication](<https://devfeed.tech/tags/replication.md>)

### AI overview

Heroku's standard Postgres plans lack logical replication, so PlanetScale's open-source Heroku Migrator uses Bucardo triggers to capture writes while it copies data and keeps the target in sync. The process starts with read-only discovery via ps-discovery and a Liftoff assessment; replicated tables need a primary key or unique index, and schema changes must be frozen during migration. After copying, the migrator rebuilds secondary and unique indexes in parallel, verifies schema and data checks, then supports a controlled traffic switch and rollback. For large migrations, version 2.0 addresses repeated full-copy restarts by separating data transfer from index rebuilding, uses TCP keepalives to detect dropped long-lived connections, and adds txntime indexes to Bucardo track tables to speed replication checks. The article reports a sample copy rate increase from about 60 to nearly 300 GB/hour, with index rebuilding taking about two hours; results depend on the database and migration conditions.

### Source excerpt

We've equipped our customers with an open source tool that not only quickly transfers your data but also provides a replication-based experience, so that any user can migrate from Heroku without extended downtime or the need to purchase a third-party product.

## Read, don't copy: replacing file feeds with OpenSharing - Part 2 (How to Implement)

DevFeed: [Read, don't copy: replacing file feeds with OpenSharing - Part 2 (How to Implement)](<https://devfeed.tech/articles/read-don-t-copy-replacing-file-feeds-with-opensharing-part-2-how-to-implement-121796.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/read-dont-copy-replacing-file-feeds-opensharing-part-2-how-implement>)

Author: Jordan Soldo; Nikhil Tallam

Published: 2026-11-06T22:13:00Z

Content type: tutorial

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [deltalake](<https://devfeed.tech/topics/deltalake.md>), [IO](<https://devfeed.tech/topics/io.md>), [copy](<https://devfeed.tech/topics/copy.md>), [CRUD](<https://devfeed.tech/topics/crud.md>), [CSV](<https://devfeed.tech/topics/csv.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [added](<https://devfeed.tech/tags/added.md>), [admin](<https://devfeed.tech/tags/admin.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [better](<https://devfeed.tech/tags/better.md>), [bi](<https://devfeed.tech/tags/bi.md>), [bi-tools](<https://devfeed.tech/tags/bi-tools.md>), [blog](<https://devfeed.tech/tags/blog.md>), [copy](<https://devfeed.tech/tags/copy.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [file](<https://devfeed.tech/tags/file.md>), [implement](<https://devfeed.tech/tags/implement.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

For Databricks-to-Databricks sharing, publish a Delta table with history in a share; the recipient mounts it as a catalog and reads it incrementally with Structured Streaming. A checkpoint lets scheduled Trigger.AvailableNow runs process only changes since the previous run, and a table update trigger can run jobs when new data is committed. Durable checkpoint storage is recommended. History is required for incremental reads; Change Data Feed is optional for the basic append-oriented path but needed for the described upserts-and-deletes path. The excerpt cautions that ignoreChanges may re-emit rows and does not propagate deletes. CREATE SHARE and CREATE RECIPIENT require metastore-level privilege. Other recipients use a credentials file; OSS Spark can use the streaming connector, while non-Spark readers pull changes by version range. The excerpt proposes validating a minimal flow with an initial snapshot and subsequent insert, update, and delete.

### Source excerpt

Many data-sharing architectures begin with a familiar pattern: A provider exports...

## Read, don't copy: replacing file and API feeds with OpenSharing - Part 1 (The Why)

DevFeed: [Read, don't copy: replacing file and API feeds with OpenSharing - Part 1 (The Why)](<https://devfeed.tech/articles/read-don-t-copy-replacing-file-and-api-feeds-with-opensharing-part-1-the-why-121795.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/read-dont-copy-replacing-file-and-api-feeds-opensharing-part-1-why>)

Author: Jordan Soldo; Nikhil Tallam

Published: 2026-11-06T22:10:00Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [copy](<https://devfeed.tech/topics/copy.md>), [API](<https://devfeed.tech/topics/api.md>), [file](<https://devfeed.tech/topics/file.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [batch](<https://devfeed.tech/tags/batch.md>), [bookkeeping](<https://devfeed.tech/tags/bookkeeping.md>), [bug](<https://devfeed.tech/tags/bug.md>), [changes](<https://devfeed.tech/tags/changes.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [clients](<https://devfeed.tech/tags/clients.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-storage](<https://devfeed.tech/tags/cloud-storage.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [compute](<https://devfeed.tech/tags/compute.md>), [copy](<https://devfeed.tech/tags/copy.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>), [data-strategy](<https://devfeed.tech/tags/data-strategy.md>), [file](<https://devfeed.tech/tags/file.md>), [insights](<https://devfeed.tech/tags/insights.md>), [sftp](<https://devfeed.tech/tags/sftp.md>)

### AI overview

OpenSharing replaces copied customer feeds with direct, in-place reads of tables stored in open formats such as Delta Lake and Iceberg. A shared table's change data feed can identify created, updated, and deleted records, while a pipeline-managed checkpoint tracks progress; access to historical data can make backfills a query instead of a customer re-export or API re-poll. The article contrasts this with SFTP file handling, timestamp bookkeeping and possible rate limits for APIs, and failures and reduced flexibility in managed connectors. Customers grant table access instead of maintaining exports, and both parties avoid duplicate storage. Readers use their own compute against cloud storage, which the text says avoids slowing the customer's systems; Databricks system tables can provide an access audit trail. The excerpt describes OpenSharing as an open protocol that does not require the reader to use Databricks, but does not provide setup details or discuss other tradeoffs.

### Source excerpt

If you ingest data from your customers over SFTP or APIs, you have probably asked...

## Data doesn't retire, it just gets cheaper to keep

DevFeed: [Data doesn't retire, it just gets cheaper to keep](<https://devfeed.tech/articles/data-doesn-t-retire-it-just-gets-cheaper-to-keep-121716.md>)

Original publisher: [Read original article](<https://www.veeam.com/blog/data-backup-last-line-of-defense.html>)

Author: Simon LIM

Published: 2026-11-06T14:13:16Z

Content type: article

Language: en

Sources: [Veeam Software Official Blog](<https://devfeed.tech/sources/veeam-software-official-blog.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [copy](<https://devfeed.tech/topics/copy.md>)

Tags: [2013](<https://devfeed.tech/tags/2013.md>), [2016](<https://devfeed.tech/tags/2016.md>), [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [accounting](<https://devfeed.tech/tags/accounting.md>), [act](<https://devfeed.tech/tags/act.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [aes](<https://devfeed.tech/tags/aes.md>), [ai](<https://devfeed.tech/tags/ai.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [apac](<https://devfeed.tech/tags/apac.md>), [asia](<https://devfeed.tech/tags/asia.md>), [asia-pacific](<https://devfeed.tech/tags/asia-pacific.md>), [business](<https://devfeed.tech/tags/business.md>), [career](<https://devfeed.tech/tags/career.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [data](<https://devfeed.tech/tags/data.md>), [government](<https://devfeed.tech/tags/government.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [immutability](<https://devfeed.tech/tags/immutability.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [ransomware-resilience](<https://devfeed.tech/tags/ransomware-resilience.md>), [retention](<https://devfeed.tech/tags/retention.md>), [storage](<https://devfeed.tech/tags/storage.md>), [veeam](<https://devfeed.tech/tags/veeam.md>), [veeam-backup-replication](<https://devfeed.tech/tags/veeam-backup-replication.md>)

### AI overview

Long-term retention across Asia Pacific should be managed as an automated data lifecycle, since records may outlast storage hardware, contracts, and the staff who configured retention. The article proposes moving aging restore points by policy from performance storage to capacity and archive tiers, keeping recovery-critical data on faster storage. It describes Veeam Vault Archive as an Azure Blob Archive based tier with policy-based GFS tiering and, in Veeam Data Platform 13.1, direct NAS ingestion and scanning before retention. The article says it is available in named regional Azure locations and has no separate transfer appliance. Tradeoffs include retrieval taking more than 15 hours, separate retrieval charges, and a 180-day minimum retention; the archive is positioned for compliance rather than rapid recovery. Tape remains supported, though its handling, rotation, transport, and restore process require ongoing manual operations.

### Source excerpt

Retention horizons across Asia Pacific now outlast the storage hardware, the vendor contract, and the career of the administrator who configured them. That makes long-term retention a lifecycle problem, not a storage problem. The post Data doesn't retire, it just gets cheaper to keep appeared first on Veeam Software Official Blog.

## Does your application need local data or faster Postgres?

DevFeed: [Does your application need local data or faster Postgres?](<https://devfeed.tech/articles/does-your-application-need-local-data-or-faster-postgres-115491.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/does-your-application-need-local-data-or-faster-postgres>)

Author: Lionel Palacin; Gülçin Yıldırım Jelínek

Published: 2026-11-03T14:55:13Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [copy](<https://devfeed.tech/topics/copy.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [Rockset](<https://devfeed.tech/topics/rockset.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [copy](<https://devfeed.tech/tags/copy.md>), [nvme](<https://devfeed.tech/tags/nvme.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [synchronization](<https://devfeed.tech/tags/synchronization.md>)

### AI overview

The article recommends measuring whether a central Postgres database meets latency and throughput needs before adding local synchronization. Sync engines use logical replication to maintain declared subsets in local stores, making covered reads local, but add lifecycle and write-reconciliation work; they suit offline use and predictable, reused working sets. AI agents make subsets harder to predict, so broad or changing sync can transfer unused data or put remote fetches back in the read path. ClickHouse Managed Postgres is presented as a faster central option using attached NVMe, with read replicas for scaling reads. NVMe does not fix inefficient queries, so pooling, query tuning, and concurrency controls still matter. For durability, up to two cross-zone standbys are supported: two use synchronous replication, while one is asynchronous; WAL archiving and backups support recovery. For analytics, WalShadow is in private preview with roughly 200 ms commit-to-visible latency, and pg_clickhouse requires configured foreign tables and supported query pushdown; it does not automatically route every query.

### Source excerpt

Local synchronization makes reads fast, but adds another data layer to manage. Explore how AI agents change the trade-off and when NVMe-backed Postgres can simplify the architecture.

## Replication for Disaster Recovery: How to Hit Tight RTOs and RPOs

DevFeed: [Replication for Disaster Recovery: How to Hit Tight RTOs and RPOs](<https://devfeed.tech/articles/replication-for-disaster-recovery-how-to-hit-tight-rtos-and-rpos-109107.md>)

Original publisher: [Read original article](<https://www.veeam.com/blog/replication-for-disaster-recovery.html>)

Author: Dylan Sams

Published: 2026-10-30T14:03:49Z

Content type: article

Language: en

Sources: [Veeam Software Official Blog](<https://devfeed.tech/sources/veeam-software-official-blog.md>)

Topics: [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [copy](<https://devfeed.tech/topics/copy.md>), [bareos](<https://devfeed.tech/topics/bareos.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [backup-and-replication](<https://devfeed.tech/tags/backup-and-replication.md>), [backup-recovery](<https://devfeed.tech/tags/backup-recovery.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [business](<https://devfeed.tech/tags/business.md>), [business-continuity](<https://devfeed.tech/tags/business-continuity.md>), [cdp](<https://devfeed.tech/tags/cdp.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [control](<https://devfeed.tech/tags/control.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [replication](<https://devfeed.tech/tags/replication.md>), [rtos](<https://devfeed.tech/tags/rtos.md>), [veeam](<https://devfeed.tech/tags/veeam.md>), [veeam-backup-replication](<https://devfeed.tech/tags/veeam-backup-replication.md>)

### AI overview

Replication supports faster disaster recovery by keeping a workload ready to start at a second site or provider. Scheduled snapshots set the recovery point interval; continuous data protection journals writes for recovery points measured in seconds, but needs supported infrastructure, journal capacity, and sufficient bandwidth. Replication must match the hypervisor, while backup supports cross-platform recovery and provides retained, clean recovery points; replicas alone do not protect against ransomware. Costs rise from backup to snapshot replication to CDP, so the article recommends assigning protection by workload. Bandwidth measures include changed block tracking, compression, WAN acceleration, seeding, and throttling. Replicas become a recovery capability only with tested, orchestrated failover plans that account for boot order, networking, and return to the primary site. For provider-hosted DR, the contract should specify who declares disaster and the provider's failover-time commitment.

### Source excerpt

Here is a question worth sitting with: when did you last prove your recovery time objective, rather than assert it? The post Replication for Disaster Recovery: How to Hit Tight RTOs and RPOs appeared first on Veeam Software Official Blog.

## Dell ties AI trust to the ability to recover clean data

DevFeed: [Dell ties AI trust to the ability to recover clean data](<https://devfeed.tech/articles/dell-ties-ai-trust-to-the-ability-to-recover-clean-data-104539.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/28/dell-connects-ai-trust-proving-data-recocvery-aicybersecurityandresiliencesummit/>)

Author: Ryan Stevens

Published: 2026-10-28T14:20:57Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [cyber resiliency](<https://devfeed.tech/topics/cyber-resiliency.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [dell](<https://devfeed.tech/topics/dell.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Security](<https://devfeed.tech/topics/security.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-cybersecurity](<https://devfeed.tech/tags/ai-cybersecurity.md>), [ai-cybersecurity-and-resilience-summit](<https://devfeed.tech/tags/ai-cybersecurity-and-resilience-summit.md>), [ai-cybersecurity-and-resilience-summit-2026](<https://devfeed.tech/tags/ai-cybersecurity-and-resilience-summit-2026.md>), [ai-cybersecurity-resilience-summit-2026](<https://devfeed.tech/tags/ai-cybersecurity-resilience-summit-2026.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-threat-strategies](<https://devfeed.tech/tags/ai-threat-strategies.md>), [ai-trust](<https://devfeed.tech/tags/ai-trust.md>), [ai-trust-and-resilience](<https://devfeed.tech/tags/ai-trust-and-resilience.md>), [aicybersecurityandresiliencesummit](<https://devfeed.tech/tags/aicybersecurityandresiliencesummit.md>), [aicybersecurityandresiliencesummit26eventpage](<https://devfeed.tech/tags/aicybersecurityandresiliencesummit26eventpage.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [attack](<https://devfeed.tech/tags/attack.md>), [automated-policy-enforcement](<https://devfeed.tech/tags/automated-policy-enforcement.md>), [backup](<https://devfeed.tech/tags/backup.md>), [business](<https://devfeed.tech/tags/business.md>), [business-process](<https://devfeed.tech/tags/business-process.md>), [christophe-bertrand](<https://devfeed.tech/tags/christophe-bertrand.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data](<https://devfeed.tech/tags/data.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [dell](<https://devfeed.tech/tags/dell.md>), [dell-technologies](<https://devfeed.tech/tags/dell-technologies.md>), [dell-technologies-inc](<https://devfeed.tech/tags/dell-technologies-inc.md>), [enterprise-data](<https://devfeed.tech/tags/enterprise-data.md>), [frontier-models](<https://devfeed.tech/tags/frontier-models.md>), [news](<https://devfeed.tech/tags/news.md>), [nyse-dell](<https://devfeed.tech/tags/nyse-dell.md>), [recover](<https://devfeed.tech/tags/recover.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [secure-ai-foundations](<https://devfeed.tech/tags/secure-ai-foundations.md>), [security](<https://devfeed.tech/tags/security.md>), [security-infrastructure](<https://devfeed.tech/tags/security-infrastructure.md>), [simon-jelley](<https://devfeed.tech/tags/simon-jelley.md>), [thecube](<https://devfeed.tech/tags/thecube.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

Dell VP Simon Jelley argues that AI trust requires recovery resilience built into business architecture, because AI expands enterprise data exposure and frontier models can help attackers chain vulnerabilities. Dell's approach uses a vault to keep recovery data off the production network and outside primary system identity privileges. Jelley says immutability or isolation alone does not prove a recovery copy is clean: organizations using vaults without an intelligence layer have recovered data containing time-bomb threats. The excerpt presents Dell's view that verifying recoverability and data cleanliness is essential to restoring business operations.

### Source excerpt

AI trust is becoming as much a recovery problem as a security one. As agents touch more enterprise data and attackers use frontier models to find weak spots faster, simply holding a copy of the data no longer proves a business can bounce back. That shift is pulling data protection out of the back office [...] The post Dell ties AI trust to the ability to recover clean data appeared first on SiliconANGLE.

## Data backup and recovery: backup vs. replication and when to use both

DevFeed: [Data backup and recovery: backup vs. replication and when to use both](<https://devfeed.tech/articles/data-backup-and-recovery-backup-vs-replication-and-when-to-use-both-106254.md>)

Original publisher: [Read original article](<https://www.veeam.com/blog/data-backup-and-recovery.html>)

Author: Dylan Sams

Published: 2026-10-28T14:08:53Z

Content type: article

Language: en

Sources: [Veeam Software Official Blog](<https://devfeed.tech/sources/veeam-software-official-blog.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [Featured-Backing Up](<https://devfeed.tech/topics/featured-backing-up.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [copy](<https://devfeed.tech/topics/copy.md>), [transaction-log](<https://devfeed.tech/topics/transaction-log.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backup-and-recovery](<https://devfeed.tech/tags/backup-and-recovery.md>), [backup-and-replication](<https://devfeed.tech/tags/backup-and-replication.md>), [backup-and-replication-software](<https://devfeed.tech/tags/backup-and-replication-software.md>), [backup-and-restore-software](<https://devfeed.tech/tags/backup-and-restore-software.md>), [backups](<https://devfeed.tech/tags/backups.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [business](<https://devfeed.tech/tags/business.md>), [data-backup](<https://devfeed.tech/tags/data-backup.md>), [data-backup-and-recovery](<https://devfeed.tech/tags/data-backup-and-recovery.md>), [data-backup-and-recovery-solutions](<https://devfeed.tech/tags/data-backup-and-recovery-solutions.md>), [database-backup-and-recovery](<https://devfeed.tech/tags/database-backup-and-recovery.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [replication](<https://devfeed.tech/tags/replication.md>), [veeam](<https://devfeed.tech/tags/veeam.md>)

### AI overview

Backup preserves historical restore points; replication keeps a standby that can resume service faster but also carries forward deletion, corruption, and encryption. The article recommends choosing protection by each workload's recovery point objective (RPO) and recovery time objective (RTO), with top-tier workloads using both. A completed backup job does not prove its contents are restorable or clean: confirm coverage, then test restore points in an isolated network with application checks, malware scanning, clean-point identification, and immutability. Enterprise recovery also requires workload coverage, database-aware processing and transaction logs, and coordinated runbooks. Veeam Data Platform is presented as managing backup and replication under one policy layer; edition capabilities differ, and the excerpt advises checking current release support before relying on specific features.

### Source excerpt

Your jobs completed last night. Retention is enforced, repositories are provisioned, and the dashboard has been green all week. None of that answers the two questions you'll get in the first 10 minutes of an incident: How fast can we be back? And back to what? The post Data backup and recovery: backup vs. replication and when to use both appeared first on Veeam Software Official Blog.

## Database Replication: Types, Benefits & How It Works

DevFeed: [Database Replication: Types, Benefits & How It Works](<https://devfeed.tech/articles/database-replication-types-benefits-how-it-works-105579.md>)

Original publisher: [Read original article](<https://talent500.com/blog/database-replication/>)

Author: Ekakshar

Published: 2026-10-28T10:51:10Z

Content type: article

Language: en

Sources: [Talent500](<https://devfeed.tech/sources/backend-archives-talent500-blog.md>)

Topics: [copy](<https://devfeed.tech/topics/copy.md>), [Database](<https://devfeed.tech/topics/database.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [transaction-log](<https://devfeed.tech/topics/transaction-log.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Debezium Connector](<https://devfeed.tech/topics/debezium-connector.md>), [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [backend](<https://devfeed.tech/tags/backend.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [database-replication](<https://devfeed.tech/tags/database-replication.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [failover](<https://devfeed.tech/tags/failover.md>), [first](<https://devfeed.tech/tags/first.md>), [helps](<https://devfeed.tech/tags/helps.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [practices](<https://devfeed.tech/tags/practices.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [replication](<https://devfeed.tech/tags/replication.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [servers](<https://devfeed.tech/tags/servers.md>), [synchronization](<https://devfeed.tech/tags/synchronization.md>), [types](<https://devfeed.tech/tags/types.md>), [works](<https://devfeed.tech/tags/works.md>)

### AI overview

Database replication copies and propagates data across database instances to support availability, disaster recovery, read scaling and regional access. The article distinguishes primary-replica setups, which concentrate writes on one primary, from multi-primary and peer-to-peer designs that distribute writes but require conflict handling; cascading replication can reduce direct primary connections while adding downstream lag. Synchronous replication waits for configured replica acknowledgements and can reduce loss of acknowledged transactions at the cost of latency or blocked writes. Asynchronous replication lowers write delays but permits stale reads and possible loss of recent changes during failover; semi-synchronous guarantees depend on what the database acknowledges. Implementation typically initializes replicas from a snapshot or backup, captures changes through logs or CDC, transfers and applies them, then monitors lag, errors and log retention. Replicas do not replace backups, since deletions or corruption may propagate. Reliable deployments also need routing and promotion procedures, tested recovery, consistency choices, access controls and cost planning. PostgreSQL, MySQL

### Source excerpt

Database Replication helps maintain data availability and reliability by copying data across multiple database servers. Explore replication types, synchronization methods, failover strategies, benefits, and challenges, along with best practices for improving scalability, fault tolerance, and disaster recovery. The post Database Replication: Types, Benefits & How It Works appeared first on Talent500 blog.

## FluidCloud replaces VDDK with its own disk copy engine for VMware exits

DevFeed: [FluidCloud replaces VDDK with its own disk copy engine for VMware exits](<https://devfeed.tech/articles/fluidcloud-replaces-vddk-with-its-own-disk-copy-engine-for-vmware-exits-102722.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4241265/fluidcloud-replaces-vddk-with-its-own-disk-copy-engine-for-vmware-exits.html>)

Author: Sean Michael Kerner

Published: 2026-10-27T17:59:07Z

Content type: news

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Disk image](<https://devfeed.tech/topics/disk-image.md>), [Cloud APIs](<https://devfeed.tech/topics/cloud-apis.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [nutanix](<https://devfeed.tech/topics/nutanix.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backup-and-recovery](<https://devfeed.tech/tags/backup-and-recovery.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [c](<https://devfeed.tech/tags/c.md>), [changes](<https://devfeed.tech/tags/changes.md>), [copy](<https://devfeed.tech/tags/copy.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [data-center-servers-virtualization](<https://devfeed.tech/tags/data-center-servers-virtualization.md>), [development-kit](<https://devfeed.tech/tags/development-kit.md>), [download](<https://devfeed.tech/tags/download.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [engine](<https://devfeed.tech/tags/engine.md>), [environment](<https://devfeed.tech/tags/environment.md>), [exit](<https://devfeed.tech/tags/exit.md>), [exits](<https://devfeed.tech/tags/exits.md>), [export](<https://devfeed.tech/tags/export.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [nutanix](<https://devfeed.tech/tags/nutanix.md>), [oci](<https://devfeed.tech/tags/oci.md>), [servers](<https://devfeed.tech/tags/servers.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>), [vmware](<https://devfeed.tech/tags/vmware.md>)

### AI overview

FluidCloud's vHOP replaces VDDK-based VMware disk copying with its own engine, while planning network and infrastructure changes before workload data moves. It exports VMDKs through standard APIs on VMware ESXi using Network File Copy, then streams them to the destination; unlike VDDK, it does not support delta sync, so each export is full. FluidCloud says snapshots limit transfer to data actually on disk, reducing transferred data about fivefold, and reports restore and image creation are twice as fast as with VDDK. vHOP remediates drivers, converts images for the target cloud, and supports parallel pipelines. Its self-service plan takes minutes; an engineer-led assessment takes three days and includes NSX firewall translation, Terraform modules, and recommended data paths. Destinations include AWS, Azure, Google Cloud, OCI, and Nutanix. These performance figures and capabilities are attributed to FluidCloud; the excerpt does not provide independent validation.

### Source excerpt

For organizations looking to migrate from VMware, the VMware Virtual Disk Development Kit (VDDK) library is a critical component. VDDK is a set of C libraries for creating and accessing VMware virtual disk files, and until August of this year, it was available as a download. That is no longer the case. Many agentless migration tools used the libraries to read virtual disks. Broadcom has said licensed use of VDDK is for backup and recovery and that it is not a customer entitlement. Organizations partway through a VMware exit are now figuring how they will proceed. It is a gap that FluidCloud is now looking to fill with the vHOP (VM Hopping Engine) service launching today. With vHOP, FluidCloud bypasses VDDK, copying disks with its own cloning engine. vHOP also maps the VMware environment, translates VMware NSX firewall policy, and generates Terraform for the target cloud before any workload data moves. FluidCloud's vHOP supports Amazon Web Services (AWS), Microsoft Azure, Google Cloud, Oracle Cloud Infrastructure (OCI), and Nutanix, and it is available now in the FluidCloud platform and through AWS Marketplace. FluidCloud emerged from stealth in July 2025, with the promise of helping organizations to migrate across clouds, with a key focus being VMware migrations. In March 2026, the company introduced its Large Infrastructure Model (LIM) technology as a way to more effectively generate, translate, and validate Terraform across multicloud deployments. FluidCloud positions vHOP as a package that covers both the network side and the data transfer side of a VMware exit. "VDDK access was just one of the hurdles from getting away from VMware," Harshit Omar, co-founder and CTO of FluidCloud, told Network World. How vHOP works VDDK lets a migration tool read the disk of a virtual machine (VM) remotely and copy only the changes after the first export, The FluidCloud engine exports the VM disk using Network File Copy (NFC) through standard application programming interfaces (A

## What a year of building ADBC drivers taught Columnar about zero-copy's non-zero problems

DevFeed: [What a year of building ADBC drivers taught Columnar about zero-copy's non-zero problems](<https://devfeed.tech/articles/what-a-year-of-building-adbc-drivers-taught-columnar-about-zero-copy-s-non-zero-problems-102641.md>)

Original publisher: [Read original article](<https://www.getdbt.com/blog/columnar-adbc-drivers-zero-copy-lessons>)

Author: Daniel Poppy

Published: 2026-10-27T17:50:00Z

Content type: news

Language: en

Sources: [dbt Labs](<https://devfeed.tech/sources/dbt-labs.md>)

Topics: [apache-arrow](<https://devfeed.tech/topics/apache-arrow.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [dbt](<https://devfeed.tech/tags/dbt.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [learn](<https://devfeed.tech/tags/learn.md>), [production](<https://devfeed.tech/tags/production.md>), [type-system](<https://devfeed.tech/tags/type-system.md>)

### AI overview

ADBC provides a shared API that returns data in Apache Arrow's columnar format, avoiding serialization when databases return Arrow natively. In production, that benefit varies: many systems still return row-oriented or JSON data that drivers must convert, and SQL types differ sharply across vendors. The article details mismatches in numeric precision, string and binary handling, timestamp time zones, and list nulls; drivers must choose Arrow mappings before seeing actual data. ADBC eases setup through TOML driver manifests and connection profiles, but the excerpt notes gaps in synchronous APIs, type support, and metadata handling. Topol recommends testing schemas early, pinning driver versions, and tracking which version is in use.

### Source excerpt

Columnar co-founder Matt Topol shares the type-system challenges of building production ADBC drivers, now used by dbt v2.

## Converting Snowflake Native Tables to Iceberg: Part 2

DevFeed: [Converting Snowflake Native Tables to Iceberg: Part 2](<https://devfeed.tech/articles/converting-snowflake-native-tables-to-iceberg-part-2-102725.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/converting-snowflake-native-tables-to-iceberg-part-2-76c3263188a8?source=rss----34b6daafc07---4>)

Author: Leo Pasta

Published: 2026-10-27T14:01:03Z

Content type: tutorial

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [copy](<https://devfeed.tech/topics/copy.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [approach](<https://devfeed.tech/tags/approach.md>), [article](<https://devfeed.tech/tags/article.md>), [assets](<https://devfeed.tech/tags/assets.md>), [can](<https://devfeed.tech/tags/can.md>), [capture](<https://devfeed.tech/tags/capture.md>), [change](<https://devfeed.tech/tags/change.md>), [cleanup](<https://devfeed.tech/tags/cleanup.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [conversion](<https://devfeed.tech/tags/conversion.md>), [copy](<https://devfeed.tech/tags/copy.md>), [counts](<https://devfeed.tech/tags/counts.md>), [covers](<https://devfeed.tech/tags/covers.md>), [cross](<https://devfeed.tech/tags/cross.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [data-migration](<https://devfeed.tech/tags/data-migration.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [native](<https://devfeed.tech/tags/native.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [tables](<https://devfeed.tech/tags/tables.md>)

### AI overview

The guide recommends side-by-side conversion: keep the native table live for validation, then cut over with a controlled rename. Freeze writes, capture grants and policies, drain streams (unconsumed stream data is lost), and verify permissions. Populate the Iceberg table either by exporting Parquet and registering files with COPY INTO LOAD_MODE=ADD_FILES_COPY, which is more efficient but limited to specified basic column types and does not support partitioned tables, or by CTAS for other types. Restore grants, policies and tags, then compare row counts and HASH_AGG values and smoke-test representative consumers. HASH_AGG requires explicit column lists and does not accept GEOGRAPHY or GEOMETRY without ST_ASWKB; equality checks are needed for certainty. Recreate streams after cutover. Keep the renamed native table as rollback fallback; reverse the rename and restore write privileges if needed, then drop it after an agreed retention period.

### Source excerpt

Part 2 of 2 -- with the pre-conversion decisions covered in part 1, this article covers conversion execution, data validation, cutover and rollback. Conversion strategy: Side-by-side Other than for initial tests and proofs of concept, side-by-side conversion is generally the right approach: Create the Iceberg table in a parallel schema, fully validate it while the native table remains live, and swap it in via a controlled rename sequence. The conversion follows five sequential steps: Pre-conversion: - Capture grants and policies - Plan and line up smoke test assets - Freeze writes Conversion - Create iceberg table (i.e. the iceberg version of the original table being converted) - Copy the data - Restore grants, policies and tags Validation (row counts, HASH_AGG, consumer smoke-test) Cutover (swap the original native table with its iceberg equivalent) Cleanup Pre-conversion tasks Confirm that you have the tools and scripts needed to smoke-test each table consumer. See "Consumer tool smoke-test" below. Generate and validate scripts to reapply all grants, tags, fine-grained access policies (like masking and row-access) on the table(s) being migrated Remove write permissions on the native table: revoke INSERT, UPDATE, DELETE and TRUNCATE while preserving SELECT (note that if the table owner is used for write, you might need to change the owner or pause the pipelines). Drain all streams on the table(s) being converted and drop them afterwards. A stream's offset can't be carried over to the new Iceberg table, so anything left unconsumed at conversion time is lost. Also confirm that the target schema exists (if not the same as the source table) and the role performing the migration has: - OWNERSHIP on source table and target schema (required for cross-schema rename) - CREATE ICEBERG TABLE permissions on the target schema - USAGE on the external volume, databases and schemas involved - If loading data via export and import (option 1), USAGE rights will be needed on the stage

## Active-Active Oracle GoldenGate Across Regions: Decide Who Owns the Data Before You Resolve Conflict

DevFeed: [Active-Active Oracle GoldenGate Across Regions: Decide Who Owns the Data Before You Resolve Conflict](<https://devfeed.tech/articles/active-active-oracle-goldengate-across-regions-decide-who-owns-the-data-before-you-resolve-conflict-100874.md>)

Original publisher: [Read original article](<https://hackernoon.com/active-active-oracle-goldengate-across-regions-decide-who-owns-the-data-before-you-resolve-conflict?source=rss>)

Author: Zalak Shrof

Published: 2026-10-26T20:30:03Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [consistency](<https://devfeed.tech/topics/consistency.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [synchronization](<https://devfeed.tech/topics/synchronization.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [copy](<https://devfeed.tech/topics/copy.md>), [crdt](<https://devfeed.tech/topics/crdt.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [2](<https://devfeed.tech/tags/2.md>), [2015](<https://devfeed.tech/tags/2015.md>), [22](<https://devfeed.tech/tags/22.md>), [active-active](<https://devfeed.tech/tags/active-active.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cdr](<https://devfeed.tech/tags/cdr.md>), [classes](<https://devfeed.tech/tags/classes.md>), [clock](<https://devfeed.tech/tags/clock.md>), [data](<https://devfeed.tech/tags/data.md>), [data-ownership](<https://devfeed.tech/tags/data-ownership.md>), [data-replication](<https://devfeed.tech/tags/data-replication.md>), [database-architecture](<https://devfeed.tech/tags/database-architecture.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [goldengate](<https://devfeed.tech/tags/goldengate.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [oracle-database](<https://devfeed.tech/tags/oracle-database.md>), [oracle-goldengate](<https://devfeed.tech/tags/oracle-goldengate.md>), [oraclegoldengate](<https://devfeed.tech/tags/oraclegoldengate.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [practices](<https://devfeed.tech/tags/practices.md>), [regions](<https://devfeed.tech/tags/regions.md>), [replication](<https://devfeed.tech/tags/replication.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Treat active-active Oracle GoldenGate as a data-ownership design problem: classify tables before choosing conflict handlers. Single-owner rows protect cross-writer invariants; escrowed quotas permit local sales within allocated limits; USEDELTA preserves numeric increments but cannot prevent overselling; timestamp or USEMAX resolution suits last-value fields but depends on reliable clocks. The described simulation found that last-writer-wins converged while losing updates, and row comparison could miss those losses; delta preserved updates yet still oversold shared inventory. The text recommends loop prevention with redo tags, before-image logging for compared columns, matching resolution in both directions, and monitoring lag, conflicts, and divergence alongside business-level reconciliation. It also notes limits including CDR's lack of support for LOBs and user-defined types, and that the simulation omits partitions, multi-row transactions, and triggers.

### Source excerpt

Oracle GoldenGate active-active replication across regions: ownership classes, CDR with USEMAX and USEDELTA, clock skew risks, and monitoring best practices.

## How to Copy Objects in Python: Shallow vs Deep Copy Explained

DevFeed: [How to Copy Objects in Python: Shallow vs Deep Copy Explained](<https://devfeed.tech/articles/how-to-copy-objects-in-python-shallow-vs-deep-copy-explained-60660.md>)

Original publisher: [Read original article](<https://realpython.com/python-copy/>)

Author: Bartosz Zaczyński

Published: 2026-09-27T14:00:00Z

Content type: tutorial

Language: en

Sources: [Real Python](<https://devfeed.tech/sources/real-python.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [copy](<https://devfeed.tech/topics/copy.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learning](<https://devfeed.tech/tags/learning.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

This tutorial explains how Python's copy module creates shallow and deep copies of objects, how those copies handle nested objects, and how assignment differs from copying. It also covers custom copying behavior and practical reasons to duplicate mutable data safely.

### Source excerpt

Understand the difference between shallow and deep copies in Python. Learn how to duplicate objects safely using the copy module and other techniques.

## On-demand compute for scheduled Copy Pipes

DevFeed: [On-demand compute for scheduled Copy Pipes](<https://devfeed.tech/articles/on-demand-compute-for-scheduled-copy-pipes-59790.md>)

Original publisher: [Read original article](<https://www.tinybird.co/blog/on-demand-compute-for-copy-jobs>)

Author: Rubén del Campo

Published: 2026-09-25T12:18:44.250143Z

Content type: release

Language: en

Sources: [Tinybird](<https://devfeed.tech/sources/tinybird.md>)

Topics: [copy](<https://devfeed.tech/topics/copy.md>)

Tags: [compute](<https://devfeed.tech/tags/compute.md>), [product-updates](<https://devfeed.tech/tags/product-updates.md>), [run](<https://devfeed.tech/tags/run.md>), [scheduled](<https://devfeed.tech/tags/scheduled.md>)

### AI overview

Tinybird scheduled Copy Pipes can run on temporary dedicated compute when ON_DEMAND_COMPUTE true is added to the datafile.

### Source excerpt

Run scheduled Copy Pipes on temporary dedicated compute by adding ON_DEMAND_COMPUTE true to the datafile.

## Desktop Settings: Removing technical jargon

DevFeed: [Desktop Settings: Removing technical jargon](<https://devfeed.tech/articles/desktop-settings-removing-technical-jargon-50478.md>)

Original publisher: [Read original article](<https://blog.thunderbird.net/2026/09/desktop-settings-removing-technical-jargon/>)

Author: Aly Blenkin

Published: 2026-09-09T15:25:40Z

Content type: article

Language: en

Sources: [The Thunderbird Blog](<https://devfeed.tech/sources/the-thunderbird-blog.md>)

Topics: [App](<https://devfeed.tech/topics/app.md>), [interface](<https://devfeed.tech/topics/interface.md>), [copy](<https://devfeed.tech/topics/copy.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [test](<https://devfeed.tech/topics/test.md>), [Users](<https://devfeed.tech/topics/users.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Sorting](<https://devfeed.tech/topics/sorting.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [content](<https://devfeed.tech/tags/content.md>), [copy](<https://devfeed.tech/tags/copy.md>), [design](<https://devfeed.tech/tags/design.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [incremental](<https://devfeed.tech/tags/incremental.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [research](<https://devfeed.tech/tags/research.md>), [settings](<https://devfeed.tech/tags/settings.md>), [sorting](<https://devfeed.tech/tags/sorting.md>), [technical](<https://devfeed.tech/tags/technical.md>), [test](<https://devfeed.tech/tags/test.md>), [thunderbird](<https://devfeed.tech/tags/thunderbird.md>)

### AI overview

The Thunderbird team describes research and incremental redesign work to make desktop settings easier to understand. It audited more than 250 content blocks, tested clearer copy with new users, and identified interface interactions that still need refinement.

### Source excerpt

Our goal for this phase of work is to remove the technical jargon, use plain language, and make it effortless for everyone to make informed decisions about their settings. With over 250 blocks of settings content to untangle, we aimed for incremental improvements rather than striving for perfection. While our previous research leaned heavily on [...] The post Desktop Settings: Removing technical jargon appeared first on The Thunderbird Blog.

## Top 8 data replication tools and solutions

DevFeed: [Top 8 data replication tools and solutions](<https://devfeed.tech/articles/top-8-data-replication-tools-and-solutions-136767.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/data-replication-tools-comparing-fivetrans-deployment-options>)

Author: Garrett Kelly

Published: 2026-08-12T16:50:42Z

Content type: comparison

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [copy](<https://devfeed.tech/topics/copy.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Data Infrastructure](<https://devfeed.tech/topics/data-infrastructure.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [elt](<https://devfeed.tech/topics/elt.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [etl](<https://devfeed.tech/topics/etl.md>), [ibm](<https://devfeed.tech/topics/ibm.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-modeling](<https://devfeed.tech/tags/ai-modeling.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [best](<https://devfeed.tech/tags/best.md>), [compare](<https://devfeed.tech/tags/compare.md>), [data](<https://devfeed.tech/tags/data.md>), [data-replication](<https://devfeed.tech/tags/data-replication.md>), [explore](<https://devfeed.tech/tags/explore.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learn](<https://devfeed.tech/tags/learn.md>), [replication](<https://devfeed.tech/tags/replication.md>), [solutions](<https://devfeed.tech/tags/solutions.md>), [tools](<https://devfeed.tech/tags/tools.md>), [top](<https://devfeed.tech/tags/top.md>)

### AI overview

Data replication copies source data to destinations for analytics, AI, or recovery; the right approach depends on freshness, scale, maintenance, and cost. Snapshot replication suits small, infrequently changing datasets; log-based CDC supports continuous high-volume updates; full replication can strain networks, while real-time streaming offers millisecond updates with added operational complexity. The eight tools serve distinct needs: Fivetran emphasizes managed connectors and low maintenance; Skyvia targets simpler cloud app syncs; Resilio handles large file systems; Striim supports sub-second streaming and in-flight masking; Hevo offers event-based pipelines; IBM InfoSphere serves legacy enterprise systems; Qlik Replicate spans mixed database environments; and Dell RecoverPoint focuses on storage recovery rather than analytics. The guide recommends defining latency needs, checking CDC and deployment capabilities, and weighing licensing alongside egress, setup, and maintenance costs. Its comparisons and recommendations are presented by the source and may not establish independent rankings.

### Source excerpt

Learn what data replication is. Explore the best data replication tools, compare pros and cons, and discover how to choose the right solution.

## Why we rebuilt our data warehouse on DuckDB over ClickHouse

DevFeed: [Why we rebuilt our data warehouse on DuckDB over ClickHouse](<https://devfeed.tech/articles/why-we-rebuilt-our-data-warehouse-on-duckdb-over-clickhouse-80692.md>)

Original publisher: [Read original article](<https://posthog.com/blog/why-we-rebuilt-our-data-warehouse>)

Author: Eric Duong

Published: 2026-06-29T00:00:00Z

Content type: comparison

Language: en

Sources: [PostHog](<https://devfeed.tech/sources/posthog.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [copy](<https://devfeed.tech/topics/copy.md>), [olap](<https://devfeed.tech/topics/olap.md>), [llamaindex](<https://devfeed.tech/topics/llamaindex.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [behaviour](<https://devfeed.tech/tags/behaviour.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [beta](<https://devfeed.tech/tags/beta.md>), [bi](<https://devfeed.tech/tags/bi.md>), [business](<https://devfeed.tech/tags/business.md>), [business-context](<https://devfeed.tech/tags/business-context.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineer](<https://devfeed.tech/tags/data-engineer.md>), [data-warehouse](<https://devfeed.tech/tags/data-warehouse.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [warehouse](<https://devfeed.tech/tags/warehouse.md>)

### AI overview

PostHog rebuilt its warehouse to support longer-running, flexible modeling queries without placing unbounded warehouse workloads on its shared ClickHouse cluster. The company says ClickHouse remains its choice for fast event analytics, but cites limitations for general warehousing: no cost-based optimizer, delayed maturity of catalog support for S3 and table formats, and query results that can vary across versions or settings. Its replacement gives each organization a single-tenant DuckDB instance that sleeps when idle and wakes for queries, with a Postgres Wire endpoint for common data tools. DuckLake stores data in S3 separately from compute, while mirrored PostHog events and synced external sources are available through the same endpoint. DuckHog lets users work on local subsets with DuckDB or dataframe tools and write results back. The excerpt presents this as a way to make data tooling and business context more accessible; the warehouse was described as a beta waitlist offering.

### Source excerpt

PostHog's original data warehouse had a single goal: delay the moment a company needs to hire their first data engineer. It did that job for a 2...

## San Diego C++ Meetup #85 - April 2026 Edition: Vector Pitfalls and Memory Management

DevFeed: [San Diego C++ Meetup #85 - April 2026 Edition: Vector Pitfalls and Memory Management](<https://devfeed.tech/articles/san-diego-c-meetup-85-april-2026-edition-vector-pitfalls-and-memory-management-51146.md>)

Original publisher: [Read original article](<https://vorbrodt.blog/2026/04/19/san-diego-c-meetup-85-april-2026-edition-vector-pitfalls-and-memory-management/>)

Author: Kobi

Published: 2026-04-20T00:54:50Z

Content type: article

Language: en

Sources: [Vorbrodt's C++ Blog](<https://devfeed.tech/sources/vorbrodt-s-c-blog.md>)

Topics: [C++](<https://devfeed.tech/topics/c-plus-plus.md>), [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [container](<https://devfeed.tech/topics/container.md>), [constructor](<https://devfeed.tech/topics/constructor.md>), [copy](<https://devfeed.tech/topics/copy.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Stateful](<https://devfeed.tech/topics/stateful.md>), [object](<https://devfeed.tech/topics/object.md>)

Tags: [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [constructor](<https://devfeed.tech/tags/constructor.md>), [container](<https://devfeed.tech/tags/container.md>), [copy](<https://devfeed.tech/tags/copy.md>), [exception](<https://devfeed.tech/tags/exception.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kobi](<https://devfeed.tech/tags/kobi.md>), [meetup](<https://devfeed.tech/tags/meetup.md>), [memory-leaks](<https://devfeed.tech/tags/memory-leaks.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [object](<https://devfeed.tech/tags/object.md>), [san-diego](<https://devfeed.tech/tags/san-diego.md>), [san-diego-c-plus-plus-meetup](<https://devfeed.tech/tags/san-diego-c-plus-plus-meetup.md>), [software](<https://devfeed.tech/tags/software.md>), [software-design](<https://devfeed.tech/tags/software-design.md>), [stateful](<https://devfeed.tech/tags/stateful.md>), [vector](<https://devfeed.tech/tags/vector.md>)

### AI overview

A report on the 85th San Diego C++ Meetup, covering C++23 quiz questions, std::vector initialization pitfalls, custom vector-like container implementation, raw memory allocation, the Rule of Five, stateful custom deleters, exception safety, and preventing double destruction and memory leaks.

### Source excerpt

Another fantastic month, another great San Diego C++ Meetup! On April 14th, 2026, we hosted our 85th session. We had an incredibly insightful meetup packed with brain-teasing code snippets, a serious deep dive into memory management, and lively discussions about the evolving tech landscape. If you missed the live session or want to revisit the [...]

## I Built a Real 3-2-1 Backup System with TrueNAS, Offsite Replication, and UNAS

DevFeed: [I Built a Real 3-2-1 Backup System with TrueNAS, Offsite Replication, and UNAS](<https://devfeed.tech/articles/i-built-a-real-3-2-1-backup-system-with-truenas-offsite-replication-and-unas-10502.md>)

Original publisher: [Read original article](<https://technotim.com/posts/321-backup/>)

Author: Techno Tim

Published: 2026-04-12T13:00:00Z

Content type: article

Language: en

Sources: [Techno Tim](<https://devfeed.tech/sources/techno-tim.md>)

Topics: [truenas](<https://devfeed.tech/topics/truenas.md>), [backups](<https://devfeed.tech/topics/backups.md>), [copy](<https://devfeed.tech/topics/copy.md>), [DIY NAS](<https://devfeed.tech/topics/diy-nas.md>), [UNiFi NAS](<https://devfeed.tech/topics/unifi-nas.md>), [UniFi UNAS Pro](<https://devfeed.tech/topics/unifi-unas-pro.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [cloud-backup](<https://devfeed.tech/tags/cloud-backup.md>), [costs](<https://devfeed.tech/tags/costs.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [nas](<https://devfeed.tech/tags/nas.md>), [offsite](<https://devfeed.tech/tags/offsite.md>), [truenas](<https://devfeed.tech/tags/truenas.md>)

### AI overview

The author built a controlled, offsite backup for a roughly 30TB homelab NAS, aiming to avoid recurring cloud costs and make recovery understandable enough to safely rebuild the main system. Their 3-2-1 goals included three copies, two media or platforms, and one offsite copy, plus straightforward individual-file restores. Cloud options did not fit their cost and recovery tradeoffs: Backblaze B2 looked expensive at this scale, while Glacier and Deep Archive retrieval costs and restore times changed the calculation. With access to colocation space and only 1U available, they chose a familiar Supermicro server bought used rather than a custom build, citing known hardware, spare parts, and platform standardization. The excerpt notes a later third copy on a different platform but does not describe its implementation.

### Source excerpt

What started as, "I just need a backup," turned into a full rebuild. I wanted a real 3-2-1 backup system for my homelab without signing up for a giant cloud bill to cover roughly 30TB of data. That ended up meaning an offsite TrueNAS box, a redesign of the main NAS, and eventually a third copy on a different platform so pulling back one file would not turn into a ZFS project. Watch the vide...

## Nim version 2.2.6 released

DevFeed: [Nim version 2.2.6 released](<https://devfeed.tech/articles/nim-version-2-2-6-released-53633.md>)

Original publisher: [Read original article](<https://nim-lang.org//blog/2025/10/31/nim-226.html>)

Published: 2025-10-31T00:00:00Z

Content type: release

Language: en

Sources: [Nim Programming Language](<https://devfeed.tech/sources/nim-programming-language.md>)

Topics: [Nim](<https://devfeed.tech/topics/nim.md>), [version](<https://devfeed.tech/topics/version.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [Closure](<https://devfeed.tech/topics/closure.md>), [copy](<https://devfeed.tech/topics/copy.md>), [return](<https://devfeed.tech/topics/return.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [announce](<https://devfeed.tech/tags/announce.md>), [async](<https://devfeed.tech/tags/async.md>), [bugfixes](<https://devfeed.tech/tags/bugfixes.md>), [builds](<https://devfeed.tech/tags/builds.md>), [closure](<https://devfeed.tech/tags/closure.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [copy](<https://devfeed.tech/tags/copy.md>), [download](<https://devfeed.tech/tags/download.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [install](<https://devfeed.tech/tags/install.md>), [nim](<https://devfeed.tech/tags/nim.md>), [release](<https://devfeed.tech/tags/release.md>), [return](<https://devfeed.tech/tags/return.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The Nim team announces Nim 2.2.6, a patch release for the stable Nim 2.2 series containing 141 commits of bug fixes and improvements. The release updates exception handling and closure iterator transformation, enables a compiler move optimization for return field expressions, and includes installation guidance and numerous fixes.

### Source excerpt

The Nim Team is happy to announce version 2.2.6, the third patch release for our stable release, Nim 2.2. It comes six months after the 2.2.4 release and it contains 141 commits, bringing bugfixes and improvements. If you're still on Nim 1.6, take a look at the version 2.0 release article to see all the features you're missing. If you've been using Nim 2.0, the version 2.2 release article shows the improvements available in Nim 2.2. The Nim 2.2.6 changelog is available here. Highlights Exception handling combined with Nim's async is more stable than ever before as the underlying closure iterator transformation has been rewritten. The compiler is now smart enough to produce a move operation for return obj.field. Previously it performed a copy. Expect your code to run slightly faster due to this and other minor performance improvements. Installing Nim 2.2.6 Check out if the package manager of your OS already ships version 2.2.6 or install it as described here. If you have installed a previous version of Nim using choosenim, getting Nim 2.2.6 is as easy as: $ choosenim update self $ choosenim update stable NOTE: We recommend you to install and use the latest version of choosenim, v.0.8.16, available in our choosenim repo. Alternatively, you can download Nim 2.2.6 from our nightlies builds. Bugfixes Fixed "=destroy for non-var failed to compile when JS" (#24914) Fixed "{.push raises: [].} doesn't respect lexical scoping" (#23355) Fixed "Pragma block disabling warning has effect beyond block" (#21975) Fixed "missing < (less than), cmp for cstring" (#24941) Fixed "[GC] Illegal storage access when collecting cycle" (#4851) Fixed "Globals in proc with static params end up being re-initialized" (#24940) Fixed "Constructor to global variable in converter generates illegal c code" (#4594) Fixed "Compile-time regression from v2.2.4 to version-2-2/devel with global variable with unhandled exception: iterators.nim(254, 11) len(a) == L the length of the seq changed while iterating

## The fellowship of the forgotten

DevFeed: [The fellowship of the forgotten](<https://devfeed.tech/articles/the-fellowship-of-the-forgotten-35655.md>)

Original publisher: [Read original article](<https://engineering.klarna.com/the-fellowship-of-the-forgotten-d341045a6123?source=rss----86090d14ab52---4>)

Author: Onno Vos Dev

Published: 2025-02-26T09:04:27Z

Content type: article

Language: en

Sources: [Klarna Engineering](<https://devfeed.tech/sources/klarna-engineering.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [2018](<https://devfeed.tech/tags/2018.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [custom](<https://devfeed.tech/tags/custom.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [erlang](<https://devfeed.tech/tags/erlang.md>), [klarna](<https://devfeed.tech/tags/klarna.md>), [leveldb](<https://devfeed.tech/tags/leveldb.md>), [memory](<https://devfeed.tech/tags/memory.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>), [serializable](<https://devfeed.tech/tags/serializable.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [source-of-truth](<https://devfeed.tech/tags/source-of-truth.md>)

### AI overview

Klarna migrated KRED from a 15 TB Mnesia cluster to Postgres with no observed downtime, using a staged transition that kept rollback possible. Sharding was set aside because surrounding systems and required components were not ready. Instead, the team preserved KRED's kdb API as a compatibility layer, added record types and null handling for Postgres, and replicated data between Mnesia and Postgres so either could lead. Batching helped Postgres replication keep pace; prepared transactions were chosen for Postgres-to-Mnesia replication because they changed less of the stable Mnesia follower logic, despite adding latency. A live key-level comparison process checked that writes and deletes converged across replicas. After the cutover, logical decoding of transaction-log messages in Postgres WAL replaced prepared transactions, requiring an upgrade to Postgres 14 and a decoder change; this reduced transaction time by about 20 ms. The authors emphasize proof of concept work, small useful steps, and extensive testing and monitoring. The excerpt says isolation-level details are reserved for a second post.

### Source excerpt

How we migrated from Mnesia to Postgres with zero downtime Back in December 2004, an Erlang application was born called KRED (referring to the freshly-started company called Kreditor, now known as Klarna). KRED is one of the "servicing systems" at Klarna and keeps track of consumer debt (among other things). It was powered by Mnesia and consisted of a cluster of 7 nodes, each holding a full copy of the database on disk. The data was replicated using a custom replication mechanism built in-house by Klarna. One node was elected as the leader and its database was considered the source of truth in the system. All database transactions were executed on the leader and writes were replicated to the rest of the nodes, the so-called followers. The Mnesia database was around 15 TB and at its peak in 2018 around 1.3 TB was held in memory at all times. Considering that few suppliers were selling hardware with such specs, it's easy to claim the crown of one of the biggest Mnesia databases in terms of in-memory storage, that was running in production. The rest of the data was offloaded to disk using mnesia_eleveldb. KRED has been a stable workhorse at Klarna so why change a winning concept? Get ready, for a two part blog post where we'll first go through our journey of how we went about this and secondly, how we made Mnesia behave just like Postgres and implemented our version serializable isolation level on top of Postgres! How the journey started Three engineers, sat down in a bar in Stockholm, Sweden and asked this question: 'When Klarna truly takes off, will KRED survive? Assuming "no", and presented with a blanco check, how would we tackle this problem?' The answer quickly revolved around the issues of running Mnesia on an even larger cluster and with leveldb compaction hitting some hot tables during peak times. One can only imagine how that problem would just continue to get worse over time. Considering the three engineers had worked on KRED for a long time, scaling KRED wa

## Integrating Snapshotter with a memory datastore in Golang

DevFeed: [Integrating Snapshotter with a memory datastore in Golang](<https://devfeed.tech/articles/integrating-snapshotter-with-a-memory-datastore-in-golang-39634.md>)

Original publisher: [Read original article](<https://www.gauravsarma.com/posts/2025-02-16_Integrating-Snapshotter-with-a-memory-datastore-in-Golang>)

Published: 2025-02-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Gaurav Sarma's](<https://devfeed.tech/sources/gaurav-sarma-s-blog.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [copy](<https://devfeed.tech/topics/copy.md>), [data](<https://devfeed.tech/topics/data.md>), [Data structures](<https://devfeed.tech/topics/data-structures.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [copy](<https://devfeed.tech/tags/copy.md>), [data-structures](<https://devfeed.tech/tags/data-structures.md>), [go](<https://devfeed.tech/tags/go.md>), [golang](<https://devfeed.tech/tags/golang.md>), [interface](<https://devfeed.tech/tags/interface.md>), [iteration](<https://devfeed.tech/tags/iteration.md>), [object](<https://devfeed.tech/tags/object.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

A practical guide to integrating copy-on-write snapshotting with an in-memory datastore in Go. It describes goals for concurrent snapshots and restore operations, outlines how snapshot state is tracked across stores and shards, and discusses possible latency and memory impacts for reads and writes.

### Source excerpt

. [Integrating a Snapshotter with a Go Memory Datastore](integrating-snapshotter-with-a-memory-datastore-in-golang-cover...

[Next page](<https://devfeed.tech/topics/copy.md?cursor=WyIyMDI1LTAyLTE2VDAwOjAwOjAwKzAwOjAwIiwgIjM4N2VmYWViLWVjOWMtNGNiYi1hOTE3LTM1YmMwMzkxOTE2YSJd>)