Blog
Data engineering, in practice.
How to move data from any source to any destination — extraction, CDC, transformation and loading, told by the team that builds Januss.
All articles
23 articlesPentaho or Januss: when it is worth keeping what already runs
Switching integration tools is rarely about features. It is about who runs the server, who maintains the routines and what happens when the person who built it all leaves.
dbt, Python or Januss: what each one solves on the data path
Comparing dbt, Python and Januss as if they were alternatives leads to the wrong choice. They cover different stretches of the data path — and what is left for your team to build changes with each design.
Python in the data stack: which part really has to be Python
Not all Python in a data stack is the same thing. One layer needs the language, another is habit, and the third is maintenance nobody hired anyone for. Tell the three apart before deciding.
Data migration: what it is, when to do it and how to keep running
Every migration looks like a volume problem until it turns into a format problem. What changes between migrating and integrating, when each approach fits and how to check the data arrived intact.
Januss or Dataddo: what each one guarantees once the data lands
Comparing integration platforms by connector count is the fastest way to choose wrong. Compare them by what each one guarantees in the destination — and by what happens when the data arrives broken.
Januss or Fivetran: what sits behind the Enterprise plan
Both read the transaction log and transform in SQL at the destination. From there they diverge on where the data runs, who writes the connector and what the bill does when volume goes over.