This document discusses optimizing a data pipeline without rewriting code. It recommends visualizing the process, breaking it down into parallel tasks, removing idle time between tasks, identifying bottlenecks, and focusing optimization efforts there. The overall process is to understand requirements, break work into parallel tasks, remove inefficiencies, identify bottlenecks, optimize those areas, and stop when performance is good enough.
4. We are
the rails and brains
of open banking
Trusted by the
industry leaders
• Natwest
• BNP Paribas Fortis
• ABN AMRO
• PayPal
• Klarna
• SEB
260 Employees
across Europe
Local offices in
• Sweden
• Finland
• Denmark
• United Kingdom
• Germany
• Netherlands
• Spain
• France
• Poland
2,500 + banks & FIs connected
We’re connected for access to all types of accounts, from banks,
neo-banks, credit cards and more, and bring them together for
you via a single, beautiful API.
Industry Authority
Member of EU, Berlin Group &
Open Banking advisory boards
ISO/IEC 27001 Certified
PSD2 Licensed
2,000 +
Platform users
30. Remember ● Use dependency based
scheduling
● Look on the metrics
● Use metrics to make your
stand
● Work with the bottleneck
once entering the code
● Stop when good enough