Application (pre-grant publication)
CONFIGURATION-BASED SYSTEM AND METHOD FOR HANDLING TRANSIENT DATA IN COMPLEX SYSTEMS
- Number
- 20240004785
- Published
- 2024-01-04
- Filed
- 2022-06-30
- Assignee
- Disney Enterprises, Inc.
- Inventors
- Melnyk; Andrew et al.
- CPC
- G06F11/3688; G06F11/3696; G06F11/3698
- Verdict
- Set aside IT transient-data handling, plumbing
- Source
- Google Patents · FreePatentsOnline
Abstract
A configuration-based system and method for handling transient data in complex systems includes a method for testing a Host App running on a user device, the Host App communicating with at least one API server using a Host App API Request, the Host App API Request including a Host App API configuration request URL, the Host App API configuration request URL being part of a Host App API Config File, the method includes selectively hydrating the Host App API Config File by selectively replacing at least one of the Host App API configuration request URLs corresponding to a query in a Test Config File with a hydrated Host App API configuration request URL, thereby causing the Host App API Request to route through Test Logic which provides a response to the Host App Request based on desired test behavior defined in the Test Config File.
Background
BACKGROUND
Engineers, product development people, design people and company management are all often working in parallel to develop a given complex data-driven software application, typically having various graphic user interfaces (GUI's or U l's), which makes it very difficult to show steady and reliable progress on such application.
This challenge is usually resolved by forming a team dedicated to creating mock data. However, such an approach results in a single point of failure and also slows down the process even further by introducing a single team to own this responsibility.
Engineering teams often work around the standard solution by creating their own mocks or “hardcoding” data as a temporary solution until the “mock” team can finish their work, or they don't progress at all until service teams are ready, which leads to teams reaching milestones at drastically different times, making the planning of large projects unpredictable.
This issue is exacerbated by contributors with different technical backgrounds and business verticals who all want to contribute but do not have the technical knowledge, skills or mechanisms to do so.
Furthermore, the standard solution is usually limited to a 1-to-1 mapping between a particular input and output making it nearly impossible to mock-out a more complex testing experience in an application which will often rely on “n” number of inputs and outputs.
Thus, it would be desirable to have a syste