Data zoning

A unified, central storage repository is provided by Data Lake. It enables applications, services, clients, and users to store virtually every transaction generated by Infor CloudSuites. A metadata-driven framework is provided to expand data processing concepts to 3rd party data sources and data sets.

These primary zoning concepts are supported by Data Lake:

  • Primary or active data zone
  • Archive data zone

Data stored within the primary zone reflects active, operational transactions generated by systems of record that a line of business most frequently interacts with. This can include data sets commonly used in reporting & analytics workstreams, machine learning quests, and extensibility. Most transactional data replicated to Data Lake is consigned to the primary zone. Data is surfaced to applications and services through a suite of interfaces including Atlas, Data Lake’s storage APIs, and the Compass SQL platform.

The archive zone is a logical construct that provides additional protections and behaviors unique to the data objects consigned to this zone. To defray costs associated with database storage, Infor CloudSuites can elect to lift & shift transactional data to Data Lake. It can delegate authority and ownership of the data to Data Lake as a means of eliminating data residency within the CloudSuite database.

With Data Lake assuming a de facto role of system of record for this data, Infor CloudSuites can append additional criteria to designate these replicated payloads as archived. Additional protections are afforded to ensure administrators do not incidentally remove or eliminate data from Data Lake

On archiving, data sets are accessible through a series of novel Compass SQL table functions. Herewith, clients can query, JOIN, UNION, and blend data across data zones. For more information on Compass SQL, see Querying the Data Lake.