In the mid 1990s I was invited onto a project where a Midwestern car rental company was implementing its first enterprise data warehouse. They assembled a team of 30 people consisting of data analysts, software developers, testers, and systems people. My job, as a consultant, was to make them successful.
I immediately realized that there would be little experience decomposing the complex ETL requirements into manageable standalone pieces for distribution among the developer team for developing and testing. This is where the encapsulation for ETL idea was born allowing individual developers to work concurrently without coding conflicts.
Further, there would be no experience for wiring together the hundreds of individual processes (written using Informix-4GL hand-code) to create an overall application that was portable, point-of-failure recoverable, load balanced, and load distributed. This is where the idea for the Mozart engine was born. I wrote the process management application and the team plugged their individual atomic processes into that application.
It seems like everyone uses whiteboards and Visio to create specifications for complex ETL applications but until now there has been no easy method to get those requirements into a utility that just runs the drawings, skipping the system level translation and programming steps. Mozart is that utility.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.