- Rock solid reliablity
- 99.9% uptime
- Fault-tolerant transaction processing
Retail payments must be reliable with high uptime.
NonStop (formerly known as Tandem) in the Guardian OS could use another, friendlier macro language. The one provided (TACL) is a bit cumbersome - and there are not practical alternatives available.
I've used it for 12 years.
There was no issues with the deployment.
This is why stock markets use it for transaction processing. Stability is what NonStop Tandem is famous for.
You can't exceed the scalability available.
Excellent. Tech support is always, repeat always, a seasoned expert engineer.
I have worked on NonStop my entire career.
Relatively challenging, for example it was difficult to configure the communications.
We used a vendor team.
If you have a high transaction volumes, it can be justified. If your transaction volumes are ordinary, this may be way too much machine for your needs. Think five million retail transactions monthly, as an example.
If you are contemplating a fault-tolerant, high uptime transaction processing machine with above normal transactions volumes - to act as a transaction server with infrequent changes to code - and you simply must have bulletproof performance - this might be the ticket. And if it is, spend a little time checking into the flavors: original Guardian OS, or the Unix OSS. Primarily languages used are TAL, C, and, yes, Cobol.