OverviewThe purpose of this report is to examine the idea of ​​transaction management and how it relates to two different database systems that I chose for the purpose of the project and for my research. I'm also looking at the different elements related to transaction management and how each of them works and what they serve in the overall scheme that is transaction management. I will look at the definition of transaction the meaning of transaction how it works the limitations and restrictions on user access. I will delve into the four properties of transactions, isolation, atomic consistency, and durability. Let's discuss transaction states and look at all six states: partially committed, failed, rollback aborted, committed, and terminated. I will also cover the aspects of concurrent execution and serizability, then detail a brief history of the two databases I chose, then do an analysis of how concurrency and recovery were implemented by both these databases with conclusion at the end with bibliographyTransactionA transaction it is an event that happens within a database and generally inserts values ​​or exports them from a database. When we look at a transaction from the point of an operating system, the transaction is analogous to processes. Although there are two classes in a data entry and read transaction, there are differences between them. When you read the information you cannot change the information or alter it in any way. But it's a different case when you enter information than the exact opposite when you alter any table or data. The Four Properties of Transactions The four properties of transactions are acidity, i.e. atomicity, consistency… center of paper… …and stored and recorded for the person storing them for any reason. Which is an improvement because I knew databases were important but I didn't quite understand how much work was needed to perform an action in a system from entry to the final stage where information is stored in a violent medium and then transferred to a more stable server And the way databases are generally considered an unimportant part of a system's operation. But they are and it's proven every time you use a website or store, do banking and access photos or videos stored on your phone, all of these things in electronic format. So, in closing, I would like to say that I have learned a lot from this report and gained a new and profound understanding of how databases are connected to the day-to-day management of sites, services and ordinary things that we take for granted in our daily lives..