Talk:Transaction processing system

What's up with having types twice?
3	Processing types 3.1	Batch processing 3.2	Real-time processing 3.3	Transaction processing

5	Types of transaction processing 5.1	Processing in a batch 5.2	Processing in real-time

add a discussion of office space
Seriously, TPS reports baby! — Preceding unsigned comment added by 152.16.225.159 (talk) 20:11, 30 May 2013 (UTC)

Clarification
I thought this article was written from an application perspective, so I added a few lines to explain the general principle, and to clarify that fundamentally transaction processing is not limited to applications but pertains to any environment where data must be maintained in a coordinated, controlled way (ACID).

Frankly, I don't believe transaction processing is limited to online processing. IMHO also some batch processes are to be seen as a series of 'logical units of work' that must be managed as transactions, and that is what database systems actually do. Rbakels 09:25, 14 October 2007 (UTC)

JAP: I agree here. A transaction processing system can be a batch system or a real-time (online) system. The basic characteristic of a transaction processing system is that it processes (surprise) transactions. Whether those transactions are processed as they occur, or at a later time is not significant to the system (though it may be to the business or to the user). So, there would be batch transactions processing systems and online transaction processing systems (OLTP)for which there is a Wikipedia entry. I suggest some rewording in the article to make it accurate and consistent with the OLTP entry.69.54.215.239 (talk) 13:54, 6 September 2010 (UTC)

Wouldn't it be more clear to write about ACID properties or about guaranteeing ACID properties or about guaranteeing them partially instead of the ominous ACID test? The Acid test is normally used to test webbrowsers or it is a name for LSD parties. --Madvermis (talk) 11:59, 14 January 2012 (UTC)

Merge proposal
I propose to merge the Transaction processing systems article into this one if any information there is relevant. It essentially is the same topic, but with a plural title. Brian Reading (talk) 09:13, 22 June 2009 (UTC)

Inflexibility?
I disagree with this. The transactions could be processed differently depending on any or all of the factos mentioned. It's all a "simple matter of programming." Peter Flass (talk) 23:55, 20 October 2012 (UTC)

Needs a lot of work
I added the definition of a transaction. Deleted the "inflexibility" section (see previous talk section) and made a few other changes, but this article is still not very coherent. Update - I've done what I can for now. I don't believe that most of the "database" material belongs here, but I'm not sure where it should go. It's a lot of good information, but just doesn't fit. Peter Flass (talk) 01:08, 13 November 2012 (UTC)

Agreed, this article needs a ton of work. Jim Gray and Andreas Reuter were able to write 1000 pages on the subject. Also agree the database material isn't really germane as a database is just another resource manager from a transaction managers perspective. The history section is also quite weak, going from SABRE/TPF to Tandem??? in a single step? A reasonable article would include such information as types of transaction models (DTP, IBM Syncpoints, etc.), more details on DTP as it is the most common model used today, and more on things like compensating transactions. Toddinpal (talk) 19:48, 11 September 2013 (UTC)

SABRE
A recent edit has change the description of SABRE from "one of the first" to "THE first" TPS. I feel that in this form the statement needs a citation, so I flagged it. Peter Flass (talk) 13:00, 21 February 2014 (UTC)

I agree. Sperry also had a transaction processing system very early. The system on the Univac 11100 (now Clearpath) was called TIP. Recently I read that early versions of transaction processors for Sperry predate the more modern 1100 series hardware and operating system (under Exec 8 which became OS 1100). Transaction systems may have actually started on the 418 and 490 and 494 series. I recall the 418 III called the 418 "Realtime" system which would indicate transaction processing. The Univac Airline Reservation and related systems built on top of TIP was called USAS. The first implementations of USAS were on Air Canada and United.

At a certain point, USAS and other the IBM airline systems went to a common format so that reservation systems could interoperate. There is a not very well documented section on USAS here in Wikipedia. In addition to reservations, TIP was used by other Univec customers such as Baby Bells under AT&T. The TIP system by the mid 1970s became known as TIP 1100 and CMS 1100 or collectively TIP/CMS. And eventually I believe it became the basis of Mapper 1100 which was a user collaboration and scripting system.

I am doing some more research in this area. Richard Katz (talk) 1:40, 17 July 2018 (UTC).

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Transaction processing system. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for //www.transarc.com/Corporate/index.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 19:57, 2 April 2016 (UTC)