As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
I am referring to design patterns as they are used in software development. We are trying to put into practice a pattern (if one exists for code developed via the DMC) that we may use as we develop our ETL processes.
The below listed link on design patterns will give you a better understanding of what I mean by patterns.
Very interesting. Altho the DMC is not a programming language it does generate FOCUS code. One could argue that by using DMC to generate Data Flows you are enforcing specific patterns. That said I haven't heard of DataMigrator customers using this methodology.
Posts: 397 | Location: New York City | Registered: May 03, 2007
My two cents on the matter: DMC provides a design pattern for the ETL process. The developer uses DMC's design pattern to create a Data Flow from pre-existing source and target data objects. Existing procedural objects can also be re-used in the Process Flow that wraps and modifies the Data Flow. DMC generates the underlying code based on the design. Every DMC design uses the same pattern - only the specific data and procedural objects change.
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007