Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Design Guide—Red Hat OpenShift Container Platform 4.2 > Financial services industry
Financial service providers that are moving from traditional monolithic applications are redefining the services that they offer their customers. Some report the need to develop and deploy stateful data services. This need can be a challenge in the cloud-native technology area, where most application containers are implemented with the presumption that container storage is ephemeral and the drive is towards stateless data services.
Large financial service providers, as well as financial transaction trading houses, tend to deploy multiple Kubernetes clusters to limit the risk of loss of service through cluster outage. Financial service providers might say that having multiple Kubernetes clusters enables load-shedding and load-distribution for greater service integrity assurance. The following information shows that OpenShift Container Platform provides better functionality than many practitioners are currently aware of.
Key concerns that financial organizations have raised with Dell EMC include:
OpenShift Container Platform 4.2 includes release of the OpenShift Service Mesh. With OpenShift Service Mesh, you can connect, secure, and monitor microservices in your OpenShift Container Platform environment.
The preferred method to provision of persistent storage is CSI. Dell EMC will provide comprehensive CSI support for all current Dell EMC storage products, as shown in Table 5.
Table 12. Usage metering
Control parameter |
Description |
MeteringConfig |
Configures the metering stack. |
Reports |
Configures the query method, frequency, and target storage location. |
ReportQueries |
Specifies SQL queries against data contained within ReportDataSources. |
ReportDataSources |
Controls the data available to ReportQueries and Reports. Allows configuring access to different databases for use within metering. |
Based on diverse field data, a typical financial services Kubernetes cluster can have
10 to 20 worker nodes, 200 to 650 CPU cores, and 1.2 to 7 TB RAM. Average CPU core utilization seldom exceeds 65 percent, which is necessary to ensure that adequate CPU cores are in reserve to handle scale-out demands. Ephemeral storage across the cluster typically requires up to 1.5 TB across the whole cluster; however, the latency of ephemeral storage significantly affects the application container user experience.