Managed Transaction Service

Red Hat Managed Services [1] simplify the deployment and operation of applications on OpenShift, for example Red Hat AMQ Online [2] configures back-end brokers, routers, resource allocation plans for queues and topics (memory, storage and CPU quotas) etc.

This RFE should examine a similar offering for applications that require transactional support.

We already have various "service based" variants of the transaction manager (JTS, LRA coordination, REST based TM, etc) which could serve as a starting point. As well as defining what such a service would "look like" and what the business value it might add, the task should focus on realising some of the goals for Red Hat managed services:

1. Simplicity; the end user for managed services tend to be very focused on achieving a specific business/application goal and they don't have the time for a plethora of configuration options, parameters etc. Therefore, the managed services typically make opinionated decisions on behalf of the user, hoping that they hit the 80/20 case at the very least;
2. Reliability and scalability through OSD [3]; OSD imposes a different collection of requirements than does OCP [4];
3. Managed services are run 24x7. The task should define what features are needed to achieve such a guarantee;
4. Integration with popular developer frameworks and languages.

[1] https://www.redhat.com/en/technologies/cloud-computing/openshift/what-are-red-hat-openshift-managed-services
[2] https://www.redhat.com/en/about/videos/amq-online-nutshell and https://cloud.redhat.com/blog/understanding-amq-online
[3] https://cloud.redhat.com/products/dedicated/
[4] https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform