Best Practices

A set of best-practices to help you get the most out of Hamilton quickly and easily.

• Function Naming
  • It enables you to define your Hamilton dataflow
  • It drives collaboration and reuse
  • It serves as documentation itself
• Migrating to Hamilton
  • Continuous Integration for Comparisons
  • Integrate into your code base via a “custom wrapper object”
• Code Organization
  • Team thinking
  • Helps isolate what you’re working on
  • Enables you to replace parts of your DAG easily for different contexts
• Common Indices
  • Best practice:
• Output Immutability
  • Best practice:
• Using within your ETL System
  • Compatibility Matrix
  • ETL Recipe
• Loading Data
  • Plugging in new Data Sources
    • Modules as Interfaces
    • Using the Config to Decide Sources