In my previous post, I briefly talked about event-based architecture for payment platform modernization and why the modernization is important to the industry. In this post, we will dive into details of the key capabilities to consider for the payment platform modernization. The capabilities covered in this post may not be the complete list but it definitely serves as a good start.
Let’s go through in detail how can we use the Kogito services to help us to modernise the payment platform by following the event-driven architecture approach. Kogito is the right fit in the scenarios where you need to implement decision services and business automation for an event driven architecture, with the fact that it is purposely built for events and cloud-native use cases.
When come to performance load testing tool, people usually think of Apache JMeter; open source, widely supported and free. JMeter with total control, flexibility and user friendliness make the perfect choice for load testing. This should be the same for load testing Apache Kafka on container platform such as OpenShift Container Platform. Let’s look at how we can use JMeter to perform Kafka load testing on OpenShift.
Running ServiceMesh or Istio on OpenShift is pretty easy as long as you understand the differences between upstream community Istio and Red Hat ServiceMesh. With the enhancements tweak for OpenShift it makes managing and running microservice applications on Istio peanut easy both for administrators and developers.
Let’s look at step by step how to enable resource monitoring on OpenShift. Container application resources monitoring is simplified with Operator Hub, Prometheus Operator and OpenShift. With the built-in resource monitoring on OpenShift, your application team will just need to focus on application development and at the same being able to get performance feedback from Prometheus on OpenShift.