The document discusses various infrastructure components and deployment types that affect system orchestration. It emphasizes the importance of data strategy, upgrade processes for compute nodes and databases, and the need for auto-healing capabilities in case of failures. Key topics include managing legacy systems, handling secrets, and ensuring data migration and versioning.

1. Presented by :
Orchestration
Trade-offs to think about
8/21/2014© 2014 Constant Contact, Inc. 1
Igor Moochnick

2. Infrastructure components
• Nodes
– Compute
– DB
– Batch
• Load Balancers
• DNS
• Etc…
8/21/2014© 2014 Constant Contact, Inc. 2

3. Types of deploys
• Uptime
• Downtime
• Distributed?
• Centralized?
• HA?
• Recovery?
8/21/2014© 2014 Constant Contact, Inc. 3

4. Data Center puppies and herds
• Primarily driven by your data strategy
– Can your data survive the data center replacement?
• Legacy systems are an anchor and center of
gravity
8/21/2014© 2014 Constant Contact, Inc. 4

5. No node access
• Bake & brew
• Code review process
• Source control auditing
• Ship logs out
• Trash your SSH keys
8/21/2014© 2014 Constant Contact, Inc. 5

6. How your upgrade process looks like?
• Compute node?
– repeatable
– reuse?
– Fry vs. bake
– Configuration management?
– Secrets?
8/21/2014© 2014 Constant Contact, Inc. 6

7. How your upgrade process looks like?
• Databases?
– SQL vs. NoSQL
– Locking and blocking
– Migration?
• Schema?
• Data?
– Versioning?
• Schema?
• Data?
8/21/2014© 2014 Constant Contact, Inc. 7

8. Failures and healing
• Auto healing?
8/21/2014© 2014 Constant Contact, Inc. 8