⚠️ Your Chrome browser version is too low. For access security, we recommend upgrade now In case of problems, please go to here Feedback.
 Re reading the classic enterprise application architecture model

Re reading the classic enterprise application architecture model

No evaluation The display of comprehensive score will take into account the authenticity of users and other factors, and the time for the comprehensive score of each work is uncertain.
eight point four 386 Evaluation Douban Reading
¥25.00

Introduction

The author of this book is the authority of object-oriented software development today. With the help of a group of expert level collaborators, he transformed more than 40 frequently occurring solutions into patterns, and finally wrote this indispensable manual on solutions that can be applied to any enterprise application platform. This book won the Production Efficiency Award and Reader's Choice Award of the American Software Development Magazine in 2003. This book is divided into two parts. The first part is a brief introduction to how to develop enterprise applications. The second part is the main body of the book. It is a detailed reference manual about patterns. Each pattern gives usage and implementation information, and is accompanied by detailed Java code or C # code examples. In addition, the whole book also uses a large number of UML diagrams to further clarify the relevant concepts.

This book is written for software architects, designers and programmers who are committed to designing and building enterprise applications. It can also be used as a reference textbook for computer majors and software colleges in colleges and universities.

Martin Fowler is an independent consultant who has used object technology to solve enterprise problems for more than ten years. His consulting areas include health management, finance and trade, and corporate finance. His clients include Chrysler, Citibank,UK National Health Service,AndersenConsulting,NetscapeCommunications。 In addition, Fowler is also an object A qualified lecturer of UML and patterns technology, he is the author of AnalysisPatterns and UML Distilled.

Catalogue of works

  1. Translator's Preface
  2. preface
  3. Mode List
  4. introduction
  5. 0.1 Schema
  6. 0.2 Enterprise application
  7. 0.3 Types of enterprise applications
  8. 0.4 Performance considerations
  9. 0.5 mode
  10. 0.5.1 Structure of mode
  11. 0.5.2 Limitations of the mode
  12. Part I Description
  13. Chapter 1 Layering
  14. 1.1 Hierarchy evolution in enterprise applications
  15. 1.2 Three basic levels
  16. 1.3 Select operation environment for each layer
  17. Chapter 2 Organization Domain Logic
  18. 2.1 Choice
  19. 2.2 Service layer
  20. Chapter 3 Mapping to a Relational Database
  21. 3.1 Architecture mode
  22. 3.2 Behavior problems
  23. 3.3 Reading data
  24. 3.4 Structure mapping mode
  25. 3.5 Mapping
  26. 3.6 Using Metadata
  27. 3.7 Database connection
  28. 3.8 Other problems
  29. 3.9 Further reading
  30. Chapter 4 Web Presentation Layer
  31. 4.1 View mode
  32. 4.2 Input controller mode
  33. 4.3 Further reading
  34. Chapter 5 Concurrency
  35. 5.1 Concurrency problems
  36. 5.2 Execution context
  37. 5.3 Isolation and invariance
  38. 5.4 Optimistic concurrency control and pessimistic concurrency control
  39. 5.5 Transactions
  40. 5.6 Offline concurrency control mode
  41. 5.7 Concurrency of application servers
  42. 5.8 Further reading
  43. Chapter 6 Session Status
  44. 6.1 The value of statelessness
  45. 6.2 Session Status
  46. 6.3 Method of storing session state
  47. Chapter 7 Distribution Strategy
  48. 7.1 The temptation of distributed objects
  49. 7.2 Remote interface and local interface
  50. 7.3 Distribution must be used
  51. 7.4 About distribution boundary
  52. 7.5 Distribution interface
  53. Chapter 8 Overall Consideration
  54. 8.1 Start from the domain level
  55. 8.2 Go deep into the data source layer
  56. 8.3 Presentation layer
  57. 8.4 Some suggestions on specific technologies
  58. 8.5 Other layering methods
  59. Part II Mode
  60. Chapter 9 Domain Logic Mode
  61. 9.1 Transaction Script
  62. 9.2 Domain ModeI
  63. 9.3 Meter module (TabIe ModuIe)
  64. 9.4 Service LaYer
  65. Chapter 10 Data Source Architecture Mode
  66. 10.1 TabIe Data Gateway
  67. 10.2 Row Data Gateway
  68. 10.3 Active Record
  69. 10.4 Data Mapper
  70. Chapter 11 Object relationship behavior model
  71. 11.1 Unit of Work
  72. 11.2 IdentitY Map
  73. 11.3 LazY Load
  74. Chapter 12 Object Relationship Structure Mode
  75. 12.1 Identity Y FieId
  76. 12.2 Foreign Key Mapping
  77. 12.3 Association TabIe Mapping
  78. 12.4 Dependent Mapping
  79. 12.5 Embedded VaIue
  80. 12.6 Serialized LOB
  81. 12.7 SingIe TabIe Inheritance
  82. 12.8 CIass TabIe Inheritance
  83. 12.9 Concrete TabIe Inheritance
  84. 12.10 Inheritance Mappers
  85. Chapter 13
  86. 13.1 Metadata Mapping
  87. 13.2 Query Object
  88. 13.3 Repository
  89. Chapter 14 Web Presentation Mode
  90. 14.1 ModeI View ControlIIer
  91. 14.2 Page ControlIIer
  92. 14.3 Front Controller
  93. 14.4 TempIate View
  94. 14.5 Transform View
  95. 14.6 Two Step View
  96. 14.7 Application Controller
  97. Chapter 15 Distribution Mode
  98. 15.1 Remote Facade
  99. 15.2 Data Transfer Object
  100. Chapter 16 Offline Concurrency Mode
  101. 16.1 Optimistic Offline Lock
  102. 16.2 Pessimistic OffIine Lock
  103. 16.3 Coarse Grained Lock
  104. 16.4 ImpIicit Lock
  105. Chapter 17 Session State Mode
  106. 17.1 Client Session State
  107. 17.2 Server Session State
  108. 17.3 Database Session State
  109. Chapter 18 Basic Mode
  110. 18.1 Gateway
  111. 18.2 Mapper
  112. 18.3 LaYer SuperYpe
  113. 18.4 Separated Interface
  114. 18.5 Registry
  115. 18.6 Value Object
  116. 18.7 Money
  117. 18.8 Special Case
  118. 18.9 Plug in (PIugin)
  119. 18.10 Service stub
  120. 18.11 Record Set
  121. reference
Loading

Everyone likes it