Showing Post From Operations
Data 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 moreGraph databases in 2026: revisit Neo4j Community, Memgraph and Apache AGE before you model another relationship in SQL joins
Most teams do not decide to adopt a graph database. They arrive at it through a query. Somebody asks “which customers are connected to that blocked customer through a shared phone number, bank account or address?
Read moreMQTT brokers in 2026: revisit Eclipse Mosquitto, EMQX and NanoMQ before you connect another device to a broker
Most teams do not choose an MQTT broker. They inherit one. Somebody installed Mosquitto from the distribution package on a small VM years ago, gave every device the same username, and it has been quietly running since.
Read moreInternal tool builders in 2026: revisit Appsmith, ToolJet and Budibase before you build another admin panel
Every growing company ends up with a second, quieter product: the screens its own staff use. Support needs to look up an order and resend an invoice.
Read more