Ryan Papineau started his career as a Service Virtualization and Test Data Management Engineer for Enterprise Projects at Alaska Airlines. When he needed multiprotocol scalable solutions for multiple databases, he combined existing solutions and created reference data at scale using engineering data. He discussed this transformation in his speech.
Table of Contents
Solutions Demo
Proxy Recorder allows you to set up a proxy between the client and your services. It gives us the ability to scale, merge and clone. It allows us to make entries in the SQL database, we can use xpath and xquery to analyze the data. It also records all interface queues in real-time.
Flight operations training
We need to train many people simultaneously. We ended up cloning aircraft so we can handle parallelism. But we also used a different approach to engineering data to create reduced flight durations – this gave us vast learning opportunities.
We took and separated our own environment called cert for short and placed all of our apps in it. We then used a test data management (TDM) tool to resolve database issues. The aircraft and the captain thus communicate with the ground station, and we solve technical IT problems and business process problems.
Flight automation
We automate the business processes performed by flight attendants and pilots and the flights themselves. It is an event model framework working in real-time.
- We take all these proxy recorders and put them into our interfaces. Now we can keep a record of data about the airline’s work.
- We have the opportunity to disconnect from the rest of the infrastructure, all databases, servers.
- We started cloning, but we started using recorded data cause the teams needed a different one.
Implementation of solutions
Ops360 is a smaller part of our flight control solutions. The tools for storing fragments here are DataGenerator and MessageReplay.
DataGenerator is an Azure Function. It works daily and is responsible for flight generation, event generation, and transformation.
MessageReplay is also an Azure Function and runs every minute. It is responsible for reading messages from the database, putting messages into specific queues, and updating rows as they are processed.
Conclusion
Ryan Papineau decided to share best practices with his listeners:
- Create an isolated environment.
- Analyze everything: architecture, code, configurations, data, events, traffic.
- Resolve data issues.
- Solve events problems.
- Use engineering data.
- Look for new solutions and think big!
