Data, Databases & Streaming

Relational & NoSQL databases, search, caches, streams, ETL/ELT, and analytics stacks.

  • 7 Subtopics
  • 15 Tracked terms
  • Last 30 days Feed window

Inside Data, Databases & Streaming

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Data, Databases & Streaming


dev.to > miruky > build-a-dynamodb-outbox-and-an-idempotent-sqs-consumer-in-the-console-1e2b

Build a DynamoDB Outbox and an Idempotent SQS Consumer in the Console

58+ min ago   (1251+ words) Introduction Hi, I'm miruky. A database commit can succeed while the caller believes... Tagged with aws, serverless, dynamodb, tutorial....


dev.to > kestre88 > backups-and-other-lies-266c

Backups and other lies

2+ hour, 52+ min ago   (177+ words) Every sysadmin I know has the same secret: we do not actually back up half the things we tell other people to back up. I have been doing this for a decade. My recovery codes live in a directory called…...


dev.to > akshay5651 > designing-offline-first-when-theres-no-server-1m4k

Designing offline-first when there's no server

3+ hour, 37+ min ago   (560+ words) I'm building an app with no backend. No accounts, no sync, no API. The database is a SQLite file on the phone, and that's the whole system. That sounds simpler than a client/server app. In some ways it is....


dev.to > akshay5651 > stop-storing-money-as-a-float-4mbc

Stop storing money as a float

4+ hour ago   (185+ words) I'm building an expense-splitting app for couples. Early on, I stored every amount as a double. It worked until two people split a ₹1,000.05 grocery bill three ways — and the app insisted someone still owed ₹0.01 that nobody could pay. The fix:…...


dev.to > bejaouibechir > clean-a-million-rows-with-hydra-etl-no-database-no-docker-nm1

Clean a million rows with Hydra ETL — no database, no Docker

4+ hour, 47+ min ago   (296+ words) A copy-paste tutorial: generate a 1M-row CSV, describe the pipeline in four small YAML files, validate it before running, then compare the Python and Rust engines. Tagged with dataengineering, python, rust, tutorial....


medium.com > @kabirbakovic > postgresql-will-let-you-invent-a-type-right-up-until-it-asks-for-a-c-compiler-67593aede3d6

PostgreSQL Will Let You Invent a Type, Right Up Until It Asks for a C Compiler

32+ min ago   (41+ words) A partner feed lands a million order rows a day, and the order date arrives as 03/15/2021. Someone stores it in a text …...


dev.to > martinhicks > dynamodb-vector-search-without-embeddings-5m2

DynamoDB vector search without embeddings

5+ hour, 48+ min ago   (553+ words) So I had a go at the geography case. The setup is a store locator, which is about the most ordinary geography question going. Seven real places stand in for shops, five in and around Leeds and two over in…...


medium.com > @mohitrai0789 > i-fine-tuned-a-0-6b-model-for-data-migration-7dcb6fbb9325

I Fine-Tuned a 0.6B Model for Data Migration.

1+ hour, 17+ min ago   (595+ words) I started Migrato because I wanted to properly learn LoRA, fine-tuning, and small language models. But I didn’t want to fine-tune a model on some …...


dev.to > devanshu_patil > why-i-keep-my-database-layer-boring-4o83

Why I Keep My Database Layer Boring

5+ hour, 52+ min ago   (551+ words) When building an application, it's easy to get excited about the visible parts. A new Compose screen. The database usually gets less attention. But while working on FinLedger, I've found that the database layer is one of the places where…...


dev.to > denis_toropov > when-the-same-reference-data-lives-in-three-services-why-we-moved-it-into-a-dedicated-service-2ll6

When the Same Reference Data Lives in Three Services: Why We Moved It into a Dedicated Service

5+ hour, 58+ min ago   (1511+ words) How to reduce data collisions when three services use different databases but rely on the same business semantics. In distributed systems, problems rarely begin with something dramatic. On paper, everything usually looks rational: separate services, separate databases, clear responsibility boundaries....