Showing Post From Databases
Embedded key-value stores in 2026: revisit RocksDB, LMDB and Pebble before you build another storage layer
Sooner or later, every backend team meets a problem that looks too small for a database server and too big for a JSON file.
Read moreSelf-service BI in 2026: revisit Apache Superset, Metabase and Lightdash before you build another dashboard
Most companies do not decide to “adopt a BI tool”. They drift into one. An analyst installs something on a spare virtual machine to stop emailing Excel files.
Read moreWide-column databases in 2026: revisit Apache Cassandra, ScyllaDB and YugabyteDB YCQL before you design another partition key
Most teams meet a wide-column database through one table that grew too fast for everything else: an event log per user, a delivery history, a feed or a “last 90 days of activity” screen.
Read moreData transformation in 2026: revisit dbt Core v1, dbt v2 and SQLMesh before you write another SQL model
Almost every reporting database has a folder of SQL that nobody fully owns. It starts with one view for daily sales.
Read moreStream processing in 2026: revisit Apache Flink, RisingWave and Arroyo before you write another consumer that keeps state
Most teams that use Kafka have at least one consumer that does more than it should. It started as a simple loop that read events and wrote them somewhere.
Read moreData ingestion in 2026: revisit Airbyte, Meltano and dlt before you write another extract script
Almost every data team has a folder of extract scripts. One pulls orders from the shop platform every night, one reads the payment gateway’s settlement API, one copies a few tables from the ERP database, and one downloads a CSV that somebody uploads to a shared drive.
Read more