From: arne@vajhoej.dk
On 11/10/2025 9:12 AM, Simon Clubley wrote:
>> In article <10eaaqr$2sqg0$1@dont-email.me>,
>> Simon Clubley wrote:
>>> z/OS has a unique set of capabilities when it comes to the absolutely
>>> critical this _MUST_ continue working or the country/company dies area.
> I like the whole CICS transaction functionality and failure recovery model.
> BTW, what is the general replacement for CICS transaction processing and
> how does the replacement functionality compare to CICS ?
(if someone reallyly like CICS then TXSeries should provide a lot of the
CICS functionality for AIX/Linux/Windows)
CICS is basically just an application server with a transaction monitor
supporting transactional components.
At the very high level VMS ACMS had (has) a similar role.
Once upon a time that was state of the art functionality.
But times has changed.
Lots of options to deploy transactional components today.
Various platform software comes with transactional support: practically
all relational databases, many NoSQL database (including MongoDB and BDB),
message queue servers (RabbitMQ, ActiveMQ/ArtemisMQ, Kafka etc.) etc..
What that means is that it is trivial for practically any language
(including script languages like PHP and Python!) to do transactions
for a single data source.
For multiple data sources XA transactions has been standardized, so data
sources and client libraries supporting XA transactions (above list minus
SQLite, MongoDB and Kafka) plus a transaction monitor and it works.
It is not even difficult to do in languages like Java, C# etc..
For those that do not like XA transactions or the platform software does
not support it, then there is the SAGA pattern and compensating transaction
model.
Yes that requires some coding, but it is a model that has been implemented
hundreds of thousands of times, so developers (working on that type of
application) know how to do it.
Arne
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
