Grid-Enabled Services Architecture
Built on a simple yet robust infrastructure, the Grid Enabled layer of the OpenLink architecture allows for highly scalable and reliable services exposing key business functions. OpenLink has based this architecture on a common infrastructure providing manageability, reliability, load-balancing, and distributed processing that can be hosted on a heterogeneous mix of Windows, Linux and Solaris. It offers computing platforms with configurations ranging from a single engine for simple service needs to multiple service hosts with clusters of grid engines for load balanced computation or data intensive services such as valuation or back-office processing. This infrastructure has supported the real-time operations at the diverse environments of our largest clients and guarantees continued support regardless of how volumes or complexity grow in the future.
Services Infrastructure
Clustered Services – The application services layer is built on a load-balanced clustering framework. Each service consists of a cluster of engines residing on single hosts or distributed across multiple hosts.
Fault Tolerance – The fault tolerance framework provides reliability and fail-over capability for the service groups. Services can have a “hot” failover implementation allowing for seamless and real-time recovery on failure.
Monitoring – The services layer has central monitoring and management capabilities and allow for monitoring of services, administration of service configuration, and management of the engines, service nodes and hosts. In addition to job sequencing and task distribution, the centralized monitoring facility actively alerts users to service layer exceptions.
Configuration – The application service cluster can be configured "on-the-fly" to adapt to varying processing demands and infrastructure requirements.
Logging – You can log requests securely for detailed auditing and reporting purposes. These logs are stored allowing for user-specified exception reporting.
Workflow – Services can be triggered by workflows, which you can construct to model business processes such as feed interfaces, End-of-Day processing or accounting. Workflows allow for sequenced operations constructed with jobs distributed to various services.
Customization – You can extend or modify services with custom business logic. Properties provide additional control over services, and allow for additional “fine-tuning” as your needs require.
Real-Time Notification – The services model supports real-time notification of system events. For services such as Real Time Positions, incremental positions are sent in real-time to various position viewers. For other services, simple notifications are sent for status updates.