|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
商品の説明
Amazon.co.jp
本書は、コンピュータの事務処理システムでよく現れるトランザクション処理について、 初歩から詳しく解説した教科書である。読者対象は大学生、大学院生とトランザクション処理の実務に携わる技術者である。
トランザクション処理システムについて、ハードウェア構成からソフトウェアまで論じている。具体的なCOBOLプログラムやCプログラムの例を含めた説明を含めている。ふんだんに図も用いていて読者の理解を助けるよう工夫している。
トランザクション処理モニターの基本的な解説を第2章で述べた後、第5章で各社の具体的な事例をページ数を費やして詳しく紹介しているところが本書の中心である。さらに複数の処理の衝突を防ぐためのロック機構やシステムのアベラビリティ(可用性)、データベースシステム回復といった話題にも章を割いている。末尾のほうで短くオブジェクト指向プログラミングにも触れている。1997年に書かれた本だから仕方ないが、これからはこの方向をもっと重視する必要があると思われる。業務ソフトウェアの世界では短期間に最新の技術を導入しにくい実情はあるにせよ、5年単位で見れば情報技術の陳腐化は避けられない。
本書には、必ずしも明快ではない箇所がそこここにある。一例を挙げれば、トランザクションとは何かを説明するところで、ビジネス・トランザクションとオンライン・トランザクションは定義しているが、トランザクション自体の定義は書いていない。読み進める過程で、何度か行きつ戻りつしないと理解しにくいというのは、こうした本では望ましくないだろう。訳本の作り方を見ても、1行の文字数が多くかつ行間も狭く、読みやすいとは言えない。日本語の文も直訳っぽいものが多く、読んでいて疲れる。新版の翻訳の際には読者にとって読みやすいものにする工夫をしてほしい。（有澤 誠） --このテキストは、絶版本またはこのタイトルには設定されていない版型に関連付けられています。
内容説明
Principles of Transaction Processing is a clear, concise guide for anyone involved in developing applications, evaluating products, designing systems, or engineering products. This book provides an understanding of the internals of transaction processing systems, describing how they work and how best to use them. It includes the architecture of Web Application Servers, transactional communications paradigms, and mechanisms for recovering from transaction and system failures.
The use of transaction processing systems has changed in the years since publication of the first edition. Electronic commerce has become a major focus for business data processing investments, from banking and stock purchase on the web, to eBay auctions, to corporate database management. New standards, new technology and products, and new languages allow web services and SOA to become the leading style of design for enterprise applications. And with the help of this book and its rich examples, you will be able to produce the state-of-the-art applications discussed within.
For more information check out Eric Newcomer's blog:
http://ericnewcomer.wordpress.com/2009/05/15/what-we-learned-writing-the-second-edition-of-the-tp-book/
登録情報
|
この商品を見た後に買っているのは？
カスタマーレビュー
最も参考になったカスタマーレビュー
23 人中、22人の方が、｢このレビューが参考になった｣と投票しています。
形式:単行本|Amazonが確認した購入
トランザクション処理の大家ジム・グレイ氏の大著（上下）を読む勇気がなかったので、ほどよい厚さの本書を読むことにしました。本書のまえがきはそのジム・グレイ氏が寄せています。過去にも類書を読んでコンピュータシステムにおけるトランザクション処理や分散トランザクション処理などに関しては、実務と会わせておおまかな知識はありました。しかし、前半１章から４章を読みこなすには、多岐に渡るコンピュータ知識、分散処理技術に関する実務経験、はてはコンピュータ・アーキテクチャの面での汎用機経験、分散処理システムの知識、経験、オブジェクト指向の知識がないと、それぞれについてはいちいち細かく解説をしていませんので、「トランザクション処理」とは何か、キューシステムとは何か、本当に読んで理解し役立てるのは困難と思われます。さらに、第５章での具体的な製品を個別に詳細に解説している箇所は、本書の売りと思われますが、前半１ー４章とそれ以外の知識がないと読み解くのは初学者にとっては難しいと思われます。現に同僚である新人の方は、本書で例示されているプログラム例は、プログラム経験がない彼にとっては、まったく読む気持ちを萎えさせるものだったと吐露しています。とはいえ、後半の第６章からは、ロック、２相コミット、可用性、複製（レプリケーションのことですね）など個別テーマを取り出して詳細に解説しているので、その筋の背景知識がある程度ある方は知識を整理するのにいいかもしれません。
いづれにしても、各ページに小さな文字で行数びっしりという体裁で、大変疲れますし、日本語が翻訳口調ですので、いらついてきます。特に発行された時より、関連するITカタカナ用語が受け入れられるようになった今日では、あえて翻訳して日本語で記載すると、かえってわかりづらいと思われる箇所が散見された印象が残ります。
初学者の方や経験者でも最新の情報を求める方には他の類書をお奨めしたいところです。
総合的に見て、トランザクション処理に携わった経験のある技術者の方が、経験の下に、原理を抽象化して知識を整理するために読むのがいいのかもしれませんが、やはり内容的に古い感じは否めません。（このような技術解説書の宿命ではありますけど）
いづれにしても、各ページに小さな文字で行数びっしりという体裁で、大変疲れますし、日本語が翻訳口調ですので、いらついてきます。特に発行された時より、関連するITカタカナ用語が受け入れられるようになった今日では、あえて翻訳して日本語で記載すると、かえってわかりづらいと思われる箇所が散見された印象が残ります。
初学者の方や経験者でも最新の情報を求める方には他の類書をお奨めしたいところです。
総合的に見て、トランザクション処理に携わった経験のある技術者の方が、経験の下に、原理を抽象化して知識を整理するために読むのがいいのかもしれませんが、やはり内容的に古い感じは否めません。（このような技術解説書の宿命ではありますけど）
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
23件のカスタマーレビュー
14 人中、12人の方が、｢このレビューが参考になった｣と投票しています。
Excellent intro to transaction principles
2004/11/19
形式:ペーパーバック|Amazonが確認した購入
This book was written in 1997 which is often considered ancient in "Internet-years" but it is still very relevant because it focuses on fundamental principles of transaction processing (TP) rather than the latest whiz-bang technologies that optimize TP.
For those of you who aren't TP experts, a transaction is a computer operation that meets the ACID test. ACID here stands for:
Atomic - the steps that comprise transaction succeed or fail as one, there is no partial success.
Consistent - the internal data structures of the system(s) remain consistent with business rules.
Isolated - the data read or manipulated by the transaction is not altered during the duration of the transaction's execution.
Durable - the results of the transaction are persisted
Why does this matter to the system user or stakeholder? The canonical example is that of the ATM machine (or the "handy bank" if you're Australian). When you withdrawl money from an ATM, it has to go out and validate you have enough funds to meet the withdrawl, reserve those funds, and dispense cash - all within the same transaction. If the ATM failed after your bank account had been debited but before you'd gotten your money, you'd be very upset; conversely if the cash was dispensed but the debit procedure failed, the bank would be very upset. Ted provides very amusing analogy for this using a wedding ceremony but you can read that in his book.
There's a whole lot more to transaction processing beyond ACID and the ATM example, including two-phase commit (TPC), high-availability, massive concurrency, and crash recovery. To find out about all of these topics, read the book. One thing to remember though is that most application developers will never have to deal with the extremely complex details of providing a working and robust transaction management implementation, but like any technology it's important to understand the technology's fundamental principles and mechanics to effectively use it.
The book itself is extremely dense. The content of the book is "only" 324 pages long but covers a large amount of ground in a good amount of detail. Definitely read in a quiet place free of interruptions with a strong cup of coffee.
One shortcoming of the book is that it was written in 1997 so it doesn't cover TP implementations in Java (e.g. JTA, EJBs, etc.) but it was nice to finally find out what the heck IBM's CICS and IMS products are.
Interestingly enough, I have never had to deal with complex transaction processing (i.e. two-phase commit) in my short IBM career. This is probably because I've worked on business-to-consumer (B2C) applications where only one data source is involved rather than a business-to-business system where multiple data sources are involved. I'll have to ask the B2B guys if they get heavy into two-phase commit or if it's not an issue.
The reason I read this book is because I've always been a bit mystified by Enterprise JavaBeans (EJBs). When I joined IBM, I knew the word, but I was not familiar with such topics as object-relational persistence, object remoting, and transaction processing, so to me EJBs were simply things that took four classes/interfaces to do what I could do in one simple POJO. Ted Neward, in a very interesting web interview on the Serverside.com mentioned that he used to think EJBs were completely worthless, but during the process of writing Effective Enterprise Java came to realize that they were not worthless but rather over-marketed. He said that they should have been called Transactional JavaBeans rather than Enterprise JavaBeans because transactions are what EJBs did very well. So, hearing this from Ted I decided to read a book on fundamentals of transaction processing, so that I could understand EJBs better. Now that I've read all about TP principles, I pick Richard Monson-Haefel's book again, and all of a sudden EJBs start to make a lot more sense.
For those of you who aren't TP experts, a transaction is a computer operation that meets the ACID test. ACID here stands for:
Atomic - the steps that comprise transaction succeed or fail as one, there is no partial success.
Consistent - the internal data structures of the system(s) remain consistent with business rules.
Isolated - the data read or manipulated by the transaction is not altered during the duration of the transaction's execution.
Durable - the results of the transaction are persisted
Why does this matter to the system user or stakeholder? The canonical example is that of the ATM machine (or the "handy bank" if you're Australian). When you withdrawl money from an ATM, it has to go out and validate you have enough funds to meet the withdrawl, reserve those funds, and dispense cash - all within the same transaction. If the ATM failed after your bank account had been debited but before you'd gotten your money, you'd be very upset; conversely if the cash was dispensed but the debit procedure failed, the bank would be very upset. Ted provides very amusing analogy for this using a wedding ceremony but you can read that in his book.
There's a whole lot more to transaction processing beyond ACID and the ATM example, including two-phase commit (TPC), high-availability, massive concurrency, and crash recovery. To find out about all of these topics, read the book. One thing to remember though is that most application developers will never have to deal with the extremely complex details of providing a working and robust transaction management implementation, but like any technology it's important to understand the technology's fundamental principles and mechanics to effectively use it.
The book itself is extremely dense. The content of the book is "only" 324 pages long but covers a large amount of ground in a good amount of detail. Definitely read in a quiet place free of interruptions with a strong cup of coffee.
One shortcoming of the book is that it was written in 1997 so it doesn't cover TP implementations in Java (e.g. JTA, EJBs, etc.) but it was nice to finally find out what the heck IBM's CICS and IMS products are.
Interestingly enough, I have never had to deal with complex transaction processing (i.e. two-phase commit) in my short IBM career. This is probably because I've worked on business-to-consumer (B2C) applications where only one data source is involved rather than a business-to-business system where multiple data sources are involved. I'll have to ask the B2B guys if they get heavy into two-phase commit or if it's not an issue.
The reason I read this book is because I've always been a bit mystified by Enterprise JavaBeans (EJBs). When I joined IBM, I knew the word, but I was not familiar with such topics as object-relational persistence, object remoting, and transaction processing, so to me EJBs were simply things that took four classes/interfaces to do what I could do in one simple POJO. Ted Neward, in a very interesting web interview on the Serverside.com mentioned that he used to think EJBs were completely worthless, but during the process of writing Effective Enterprise Java came to realize that they were not worthless but rather over-marketed. He said that they should have been called Transactional JavaBeans rather than Enterprise JavaBeans because transactions are what EJBs did very well. So, hearing this from Ted I decided to read a book on fundamentals of transaction processing, so that I could understand EJBs better. Now that I've read all about TP principles, I pick Richard Monson-Haefel's book again, and all of a sudden EJBs start to make a lot more sense.
13 人中、11人の方が、｢このレビューが参考になった｣と投票しています。
clear, concise and practical
2002/1/14
形式:ペーパーバック
I have been using this book in the advanced undegraduate class series on Transaction Processing. Since this book, as emphasised in the preface has eveolved from the class material, it is exemplerary suited for that purpose. But not only in academia, this book has enought coverage to provide a first reference point in such topics as TP monitors, queue design, locking solutions, HA and recovery in databases, 2PC. Additionally, VERY usefull (if somewhat dated) industry survey of Transaction Monitors (this will really benefit to the other edition perhaps including app servers and EJBs). Highly recommended.
5 人中、5人の方が、｢このレビューが参考になった｣と投票しています。
A very good introduction into TP concepts
1999/3/26
形式:ペーパーバック
This book is a very good introduction to transaction processing. It did a wonderful job of explaining concepts, and gave concise, clear examples. I would recommend this book as a primary text for anyone wanting to get an overview of the main TP ideas, with the Gray & Reuter book as a supplemental text. The book is very readable, too.
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
リストマニア
|
|
関連商品を探す
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
