Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
Keeping Data and Integrations in Sync by Steve Hackley This presentation will discuss the challenges and potential solutions for refreshing multiple application environments (Development/Staging/UAT/etc.) with data from a Production database, while keeping some amount of table data intact from the prior database after the Production restore. When not white boarding out solutions with his team, Steve Hackley can be found with the hiking boots on traversing the switchbacks of the Appalachian Trail, or cooking out on the deck at home. With almost 20 years of web development and management experience in all areas including pre-sales, strategy, consulting, operations, and development, Steve has been responsible for assembling and leading several development teams implementing various technologies ( .Net Stack, BI technologies, Ruby on Rails) for clients believing in the notion 'work smarter, not harder'.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In Steve Hackley's presentation titled 'Keeping Data and Integrations in Sync,' delivered at RubyNation 2017, he addresses the challenges associated with synchronizing multiple application environments—such as development, staging, and UAT—with production database data while retaining some table data from the previous database state. Hackley emphasizes the importance of having production-like data in development environments to aid in debugging and development processes. Key points discussed in the presentation include: - **Integration Challenges**: When pulling production data into staging or development environments, critical pointers and foreign keys often become environment-specific and may get lost during the restore process. - **Proposed Solutions**: Hackley proposes utilizing an external database that stores key-value pairs to reconnect these pointers after restoring a production snapshot to maintain the integrity of integrations. - **Maintaining Historical Data**: Access to production data allows developers to handle historical data effectively, which is beneficial for creating reports, workflows, and troubleshooting edge cases. - **Working with Payment Systems**: He illustrates the challenges of linking customer identifiers across different environments, using the example of integrating with payment providers like Stripe. Each environment generates distinct customer IDs for the same entity, necessitating the need for a method to link them. - **Implementation Process**: Hackley explains their current implementation, which uses Ruby scripts to import and sync key-value pairs across environments, emphasizing the need to scrub sensitive information before moving production data to staging. - **Data Scrubbing**: The process involves ensuring that sensitive information is encrypted or anonymized to prevent exposure in less secure environments. - **Scheduling Syncs**: They establish a routine process for syncing data, which helps maintain data integrity and relevance across environments for effective workflows. In conclusion, Hackley underscores that maintaining data accuracy and synchronizations between integrated systems not only enhances debugging but also accelerates development cycles. He encourages further conversations regarding data handling practices and the syncing process, emphasizing the importance of effective data management in modern web development environments.
Suggest modifications
Cancel
