FX Rate Pipeline: Dockerized In-Flight State Management
An intentionally flawed ETL pipeline built with Apache NiFi and PostgreSQL inside Docker, designed to surface and demonstrate the architectural limitations of in-flight stateful transformation — and why the industry moved from ETL to ELT.
A question. A process.
Work you can explore.
Move from the project’s purpose to its available previews and source files.
Chapter 1 of 4 · The question
What this project explores.
An intentionally flawed ETL pipeline built with Apache NiFi and PostgreSQL inside Docker, designed to surface and demonstrate the architectural limitations of in-flight stateful transformation — and why the industry moved from ETL to ELT.
Follow the implementation.
The repository documents FX Rate Pipeline: Dockerized In-Flight State Management. Start with the README and follow its setup and implementation files; the source collection below gives you a way into the work.
Read the implementation notesLook beyond the project summary.
The source files and README are the available evidence for this project. Open them to review the implementation and its assumptions.
Choose where to look deeper.
Search the linked source inventory or narrow it to the kind of artifact you want to inspect. Files open at their original source.
4 linked source files
No linked files match this view.
The source
keeps moving.
Source updated
An intentionally flawed ETL pipeline built with Apache NiFi and PostgreSQL inside Docker, designed to surface and demonstrate the architectural limitations of in-flight stateful transformation — and why the industry moved from ETL to ELT.
Current README excerpt
[](https://www.docker.com/) [](https://nifi.apache.org/) [](https://www.postgresql.org/) [](https://www.frankfurter.app/) [](LICENSE)
A source excerpt, not an independently verified outcome.