A survey on recent developments of a specific area in transaction processing - Essay Example

? A Survey on Recent Developments in Transaction Processing Introduction There are three types of transaction processing the first is Interactive or Online Transaction (Mohr & Thomas, 2003), this would include online games, Voice and Video calls. The second type of transaction processing is the information access, wherein there is only one set or pair of request from the client and the server providing the information. The third type of transaction which is normally done with a database component is the read/write transaction (Gray & Reuter, 1993). The last type of transaction normally reads the information transmitted to the client after a request has been made by the client and the same client update the information and the update is then transmitted to the server for processing (Kirsten, Ihringer, & Kuhn, 2003). Over the years, techniques have been developed to resolve issues in security, speed and integrity. This would include client-server computing, object-oriented computing, relational database management systems (Myerson, 2002). Over the years several ways of accessing information have been developed as well. Work stations of the oldest mainframe to the current ipads or even mobile phones that enable the clients to access information and data anywhere anytime the way data is accessed have been progressing as well. Clients are generally the users accessing or requesting access to information with the use of devices such as mobile phones and other computing equipment. Keeping expediency and efficiency in mind Clients now-a-days are always on the go, accessing information along the way or even while in transit to another location to perform their job function. These types of client behavior will be the focus of this paper and the study of the various ways or techniques in accessing information that is needed in their job. Discussion There are several complexities in the current computing environment and that would include mobile computing. Exacerbated by the fact that clients or users making use of mobile devices such as cellular phones, ipads and laptops with wifi access are already on the go, security considerations as well as concurrent data accessing are also included in the list of complexities. The model described in the paper of Dunham, Helal and Balakrishnan in particular the Kangaroo Model (Dunham, Helal, & Balakrishnan, 1997) and its derivatives will not only expose the integrity of the data it could also increase the computing power requirement from the server side because of the number of active transactions or sessions (JT) created by the single data request as the client moves from one place to another within the sphere of the Network. According to the Kangaroo model as described, the termination of each of the Joey Transaction or JT is dependent on the termination of the last JT. If however the JT somehow failed to terminate for one reason or another that would include loss of power, loss of signal. The Joey Transactions will be open occupying precious resources of the server. The solution to the mobile transaction process described in the paper may have been a viable option at the time of its writing. However, newer technology as well as better solutions has been proven to work as effectively to address the mobile computing challenge. The advent of the internet protocol has made streaming transaction possible using mobile devices in any bandwidth and in any type of network SLA (Service Level Agreement – efficiency) or even QoS (Quality of Service). Over the years strategies or concepts have emerged to augment if not enhance the computing experience using the Internet Protocol which would include: Client-Server A more prudent solution would be the client-server model (Kanter, 1997) wherein, client based transactions are done at the client side and the server’s would just be delegated to providing server management and data record access from the database. The client-server model will also limit the role of the network system to data transmission during requests from the client side and filling of the request by the server. The solution described herein would simplify the model since when a request is made from the client side, the server or the application interfacing with the client request will create a session that will populate all the fields required by the client from the database into a screen output. The database could be distributed or singular but the information will be culled into the screen output that will be sent to the client through the application running in the server. Once the screen output is transmitted the session created by the request will be closed by the server. In re-establishing the connection to the servers in particular the session that was accessed last by the client the cookie stored in the client’s computer will provide the connection and all other session related information. To illustrate the client server model in a simplified manner using the example provided in the paper. The adjuster will access the record of the car from the central server, the application from the server side will cull or collect all the data related to the request of the adjuster. Then the application will dump all the records of the requested transaction to the mobile unit of the client. The server application will also send a cookie to the client’s mobile unit if in case there is a need to re-establish the connection. The cookie will provide the logical address of the server, the password needed if in case the application will require for the client to login to the system. The adjuster if in case she wants to update the information stored in the server, simply uses her thin client application to edit the information stored in her mobile unit. With all the information edited or appended by the adjuster completed, the adjuster simply re-establishes her connection by entering or “sending” the revised information to the server. The client-server solution will therefore limit the role of the network and all the other problems associated with it. The client-server solution will also limit any error or ambiguous transmission associated to data streaming. To stress the client-server solution will also maximize if not optimize the resources from the client side and also from the server side. The server will concentrate its effort in managing the application, filling client requests, and managing the database if in case there is a need for it. The client side of the whole process will use its computing power in processing the entries made, that would include verification, validation and authentication. There are instances when the client side of the application will also prepare the variables or entries for transport to the server. These variables are then encapsulated in an IP packet and sent to the server. The application in the server itself will then update the respective databases as required by the data transmitted from the client. Complications arise when two or more clients access the same record. Which is resolved by simple solution called “last update is the latest update”. To resolve integrity issues, an audit trail is normally set-up for auditors to review later. To resolve the correct which data is correct a posting program is normally ran. Several permutation of the client server solution to resolve issues in mobile computing as well as computing resource efficiency have been developed using both hardware and software. Data Streaming The cited example by Dunham, Helal, & Balakrishnan in 1997 is more apropos to data streaming commonly used in multi-media transactions if not in video and voice transmission that calls for real time interactive communication between the server, another mobile unit or other infrastructure resource. The IP model or internet protocol have provided the best solution for this type of transaction. This method will convert voice and video into its digitized voice, video or even screen output. The converted file will then be encapsulated in an IP packet the IP header normlly contains the IP of the intended receipient that will then reconvert the data into its normalized format. The two essential component of a data streaming solution is the computing power of the mobile unit and the transmission bandwidth that would enable for live, interactive data streaming. With the use of the internet protocol the IP address will enable the system to track the whereabouts of the mobile units engaged in data streaming transactions. Since the IP address of each mobile unit is unique. Broadcasting or propagation can be done initially but if a return token is returned via a specific route that route will be used until such time that it is not viable anymore. Or if there is no more return token that is being sent back through that line. This way it will be more efficient for the transmission system most especially in bandwidth utilization management. The same technique can be used when downloading large files from a server to a computer or mobile devices. The data can be encapsulated in an IP packet to ensure that all parts of the large file is downloaded. The receiving mobile computer can then assemble the file within his unit. Batch Processing Batch processing is one of the oldest if not the oldest transaction methodologies in use not only in computing but also in other processes that requires manipulation of large amounts of data or records. To illustrate: In the context of computing, meter reader normally scans the meter to get the current reading of gas, water and electric meters. In reading the meters of the units in a condominium building that are normally located in the basement of the building that does not have any wireless connectivity meter readers of utility companies normally stores what his handheld device have stored until the meter reader can acquire a signal again. The above is only possible if the mobile hand held device has an independent application running that can read and store in a temporary file the data that has been gathered. Other forms of Transaction Models The following are some types of transaction mentioned by Gray and Reuter in their book Transaction Processing Concepts and Techniques (Gray & Reuter, 1993). Although basically the following are just permutation if not derivatives or a combination of the three major types of transaction we shall mention it here as well. The use of mobile devices have been very common in particular wifi and cellular phones the following types of transaction can very well be applicable to mobile transactions. Chained Transaction Chained Transaction (Coronel, Morris, & Rob, 2009) opens a list of tables or databases from a single page of variables with each variables opening different tables or databases. In the context of mobile environment the client server solution would be able to resolve the problem of chained transaction. The server side of the application would be able to open and access the data using the transaction that is sent over by the client. Nested Transaction Nested Transaction (Moss, 1985) by its definition means a series of transaction that imbedded within each transaction. In the context of mobile computing a solution, each nested transaction will be treated as one transaction with a cookie assigned to it. Another solution would be to let the server side of the application handle the nested instructions. There is however a caveat in nested transaction most virus detection system detect these type of transaction as a virus. Since for all intents and purposes nested transaction do not have any practical use. Distributed Transaction Distributed transaction (Ozsu & Valduriez, 2011) is when several databases or system resources or even servers are accessed by a single transaction. Distributed transaction in the context of mobile computing will be solved by a client server solution. The application server in a distributed solution will be the one to manage the access and retrieval of data from the resources that contains the data required by the transaction. Efficiency and extra computing power are the reason why distributed transactions are used in an application most particular in a client server environment. Reporting and Co-transaction model Reporting and co-transaction (Hein, 2006) model is a top level type of transaction that is symbiotic to other transaction. It act basically as a reporting transaction of another transaction that in-turn could be the main transaction or executing transaction. This model is normally found in mobile telephone system that executes several stringed transaction of a single call. Basically used to gather and report statistical data of the transaction that caused it to be executed in the first place. To illustrate: when a call is made by a cellular transaction the first transaction initiates and connects the call to the other phone user. Once completed the same call generates several more transaction that would include a reporting transaction. The reporting transaction includes statistics with regards to the first transaction that recorded the time, the location and the duration of the call. Pro motion transaction model This type of transaction supports the mobility of the transactions in a mobile phone system. Basically it is a nested transaction model and used in sustaining disconnected transaction. Several reporting transaction is generated by this model however, this transaction model main aim is to constantly establish connection with a database to support the call. To illustrate: When a call is made by a pre-paid number, the first transaction is generated to determine if the pre-paid phone still has balance in its pre-paid account. The data is held by a database that is completely separate from the mobile switching system. Once completed a return transaction is then generated to the mobile switching system that then allows the connection. Several encapsulated transaction is generated by the transaction as the call progresses since the balance of the account needs to be constantly monitored to ensure that the call is still supported by the amount in the database. This transaction is still described by Hein Nam Le in his thesis published in 2006 in Norway. Weak-Strict Transaction model Weak strict transaction model can be likened to a propagated or replicated update of databases as each mobile host is given a copy or the transaction is replicated at each mobile host in a cluster. The weak copies are used as the mobile user moves from one host to another. The strict transaction is then use to update when there is a need to commit any change. If in case there is a conflict between the weak transactions, the final arbiter will be the strict transaction. It should be understood that weak transaction could have several different changes made as the mobile user passes through one mobile host within the cluster. As soon as the mobile transactions is cancelled or completed the strict transaction will then cull all the changes in the weak transaction and compare it with strict transaction before it is committed. Pre-write Transaction model Pre-write transactions propagate information or pre write updates and replicate it in the mobile hosts within the network. The pre-write transaction is the best possible solution to a truly mobile and moving mobile user. When the current transaction is cancelled or terminated, the database will be updated by the final commit transaction that will define the data or information that needs to be updated in the database. Standards for Transaction Processing Other types of transaction might exist, however as discussed above these are just permutation if not a combination of the types of transaction described previously. It should be noted that IP and client server solutions are ACID (Atomicity, Consistency, Isolation and Durability) compliant (Gray & Reuter, 1993). However, ACID are normally a function of programming. Server application normally provide for validation that conforms to the ACID standard to ensure the integrity of the data in the database. The client side of the transaction normally gathers data and conduct authentication and validation. Once the data is transmitted to the server side another validation is conducted by the server to ensure that the transmission has been completed. IP packets by its very nature can arrive using several routes that are intended for a single IP. Culling the packets to form and complete the transaction is a function of the server application. Most application has already provided ways to implement solution to guarantee compliance to ACID. It should be noted that IP packets are sent and received by clients and servers respectively depending on the available bandwidth or network. The transmission protocol itself ensures that a file is deemed only complete and accessible to the server application when all the packets have been received by the system. The very nature and design of the IP and client server computing have already provided a way to conform with the requirement of ACID. Summary Transaction processing in a computing environment has made great strides over the years. The current techniques and solutions have already taken into consideration the deficiency if not the limitations of the current infrastructure technology to achieve the level of service demanded by the computing public. Thus, when the new set of network technology came in which is much more faster and efficient the transaction cycle not only improved dramatically but it also called for the realization of what previously have been thought to be in the realm of pseudoscience or science fiction. Transaction types have remained the same over the years. Online interactive or real time communication or transaction, batch processing and the client-server are still the major types of transactions. Even with the advent of the new set of infrastructure these transaction types remain the same. Real time transaction or interactive transaction is now delegated to multimedia, voice and video streaming. The technological strides mentioned above have made the different methodology and techniques in transaction processing more efficient. Employing a combination of the type of technology and employing multiple techniques in data processing will make transaction processing more responsive to the need of the application (Icon Group International, 2009). To illustrate: social networking site normally have chat rooms where it is possible for friends using the site to chat with each other. Data Streaming using IP packets can make it possible for the chat to be done in real time. However, Chat rooms have historical conversations. Using a combination of the client-server and data streaming techniques will enable chatters to review previous conversations and at the same time make the current conversation real time. Bibliography Coronel, C., Morris, S., & Rob, P. (2009). Database Systems: Design, Implementation and Management . Washington: CENGAGE. Dunham, M. H., Helal, A., & Balakrishnan, S. (1997). Mobile Transaction model that captures both the data and movement behavior. Mobile Networks and Applications 2 , 149-162. Gray, J., & Reuter, A. (1993). Transaction Processing: Concept and Techniques. San Francisco. CA: Morgan Kaufman Publishers, Inc. Hein, N. L. (2006). A Transaction Processing System for Supporting mobile collaborative works. Trondheim, Norway: Norwegian University of Science and Technology. Icon Group International. (2009). Relational Database Management System: Time Line History 1970 - 2007. New YOrk: Icon. Kanter, J. P. (1997). Understanding Thin Client/Server Computing (Strategic Technology Series). Washington: Microsfot Press. Kirsten, W., Ihringer, M., & Kuhn, M. (2003). Object-Orinted Application Development Using the Cache Postrelational Database. Germany: Springer Verlag Berkin. Mohr, N., & Thomas, G. P. (2003). Interactive Broadband Media: A guide for a successful take-off. Weisbaden: Friedr, Vieweg & Sohn Verlagsgesellschaft mbH. Moss, E. B. (1985). Nested Transaction: An Approach to Reliable Distributed Computing. Boston: MIT Press. Myerson, J. (2002). The complete book of middleware. New York, USA: CRC Press. Ozsu, T., & Valduriez, P. (2011). Principles of Distribute Database Systems. Ontario: Springer. Read More