Eventually, the Cache will be replaced by equivalent functionality running on the Fabric.This more detailed architecture diagram shows multiple services grouped together into districts:The original UI service that handles all user generated requests is still in place.
We can trace the roots of each district back to the services in our original high-level architecture diagram.There are three main persistence solutions used within Workday. These services also act as in-memory databases and load all data on startup.
Customers typically use this time to evaluate business processes and reporting features. The Reporting Services were then enhanced to support additional tasks such as payroll calculations and tasks run on the job framework.A number of other persistence solutions are used for specific purposes across the Workday architecture.
Customers may continue to use Customer Central to manage deployment projects for additional Workday products or to support a phased roll-out of Workday.All of these persistence solutions also conform to Workday’s policies and procedures relating to the backup, recovery, and encryption of tenant data at rest.Workday’s multi-tenant architecture enables a unique approach to deployment.
Click play on the video below to see each service added to the architecture.Workday provides sophisticated tools to support new customers’ deployments.
Working in conjunction with the customer, deployment partners select from a catalog of pre-packaged configurations based on which products they are deploying.
We are currently building out a fabric based on Apache Ignite which will sit alongside the Cache. It also means that our JavaScript and UI service developers can focus on building the front-end components. For example, more of the Transaction Service load is being distributed across other services. Workday was developed with integrations in mind from the start.
Deployment partners get access to a range of deployment tools through Customer Central.
As with any other city, there are districts with distinct characteristics. Integrations access the Transaction Service and Reporting Services through the API Gateway.The Integration Services provide a way to synchronize the data stored within Workday with the many different systems used by our customers. Initially, the focus is on the consulting ecosystem.
As these tools reach maturity, customers gain more access to these features and functionality. Workday’s UI is rendered using HTML and a library of JavaScript widgets. Over the years the OMS has expanded to become a collection of services that manage a customer’s data. Many pre-built connectors are provided alongside a variety of data transformation technologies and transports for building custom integrations.
The data is provided in tabular form and consultants use CloudLoader to transform, cleanse and validate it before loading it into the customers’ tenant.Integrations are managed by Workday and deeply embedded into our architecture.
A typical integration will transform the data to a file in Comma Separated Values (CSV) or Extensible Markup Language (XML) and deliver it using Secure File Transfer Protocol (SFTP).
The UI Services use the metadata to select the appropriate layout for the client device. At run-time the lens is converted into a Spark SQL query which is run against the data stored on HDFS.Zooming in on the User Interface district allows us to see the many services that support Workday’s UI.Deployment starts with the creation of a foundation tenant. Once a lens is created, it can be used as a report data source just like any other data within the Transaction Server. A depiction of these connections resembles a city map rather than a traditional software architecture diagram. These services run integrations developed by our partners and customers in a secure, isolated, and supervised environment.
Magellan Health is building the Connected Enterprise, with self-service, AI-powered integration at the centerCloud-based applications adapt and grow with organizations of any size, providing a scalable solution without continual data and system migrations. Performance Statistics are also collected by Kafka.
The schedule for an integration is managed by the Transaction Service.