A Customizable Schema Ensures Your Automation Delivers Technical and Business Value
As groups continue to evolve their automation practice, they inevitably encounter business data that doesn’t fit into predefined schemas. This is usually a symptom of an outside developer having an opinion that doesn’t capture the nuances of a specific industry or a business they aren’t familiar with. Unfortunately the best option for these groups is to modify the application or relegate their important business data into rigid custom fields. Once this happens business data is no longer treated as a first-class citizen, often losing flexibility and suffering from reduced usefulness. That’s where the power of being able to control your own schema gives teams new-found powers.
Here are a few reasons you want full control over your intent data schema:
- Industry-Specific: Teams that need to track more proprietary data can easily include that in their data.
- Multi-Vendor: When multiple vendors are involved, conflicting or incomplete schemas can result in missing data.
- Cross-Domain: Platform-specific applications can yield data gaps, such as when dealing with cloud and on-prem deployments.
- Disparate Systems: Too often disparate systems result in data silos. Flexible schemas allow for data from multiple systems to exist simultaneously within a single platform.
You can read more about Infrahub’s flexible schema and how to supercharge your data, within the Infrahub documentation. Meanwhile, check out this short demo video that we created for Autocon2 where we take a look at how easy it is to update a schema to include new attributes.