AcidTransaction (ACID)
The transaction is a sequence of operations performed by a single logical work unit. The ACID transaction must have four properties, called the ACID attribute:
• Atomicity. The work unit is not sluggable; either perform all data modifications or no data modifications. • Consistency. After the transaction is completed, all data must be consistent. • ISOLATION. The data of the middle state cannot be seen outside of the transaction. • DURABILITY. After the transaction is completed, its role will be kept permanently in the system.
Atomic Transaction (atomic transaction)
See the ACID transaction.
Business Docunment (Business Document)
Also known as documentation.
From a technical point of view, it is an object that defines the function parameters and / or returns values provided by the service.
From a logical perspective, it is a logical information unit used in business transactions, such as purchasing orders.
Business Entity (Business Entity)
Business entity is an object that implements business rules in the system.
Business Entity Layer (Business Communication)
The business entity layer is composed of a business entity that performs the work steps defined in the process.
Business Process
Also known as processing.
A group of related activities that reach a certain business goal is correctly implemented.
This processing is integrated or coordinated to reach a series of activities required for a certain business objective.
Business Processing Performs some operations by step to make the system from one state to another state. At each step, business processing can perform a business operation.
Business Process Layer (Business Processing Layer)
Define business processing within the business service; it uses the business entity layer to perform the operation.
Business Process Service (Business Processing Service)
The main function is a service that is integrated or coordinated by other services.
Business Service
The main function is a service that is executed; it is usually managed by processing services.
Component
A functional unit that can be performed across multiple implementations. Provide one or more interfaces and software objects that implement logic.
Contract (Agreement)
Describe all constraints of all constraints of any session between two services; including all design time constraints and runtime constraints.
Conversation
There are two services about a particular topic or business entity.
An instance of the agreement, two of which are involved in transmitting and receiving messages mutually.
Coupling (coupling)
Coupling represents the linkage of things - that is, they are dependent, and if things have changed, a series of results will be generated.
Two services are binding the tightness of the tightness.
Data Accessor (Data Accessor)
Data Accessor uses a stored procedure to access data in the database, and store this data for business services.
Data Repesentation Layer (Data Representation)
The data representation layer contains a data accessor.
Durable State (persistent state)
State in a persistent medium (eg, a file system or database).
Emissary (messenger)
PAT Helland's design patterns for service, its main function is to help prepare to submit requests to other services, and help interpret the response of the service to request.
FIEFDOM (area)
PAT Helland is a designed pattern proposed for a set of loosely coupled services, which packages shared and deployed together.
Idempotency (Power and the Ministry)
An implementation mode, in this mode, whether it is received or received multiple times, it has the same effect.
Long Running Transaction (Long-term running transaction)
Also known as SAGA (series records).
The implementation of business processing or partial business processing, which contains logic that compensates for activities that have been executed at the time of cancellation.
Message (message)
Information units transmitted from one service from one service from one service.
Policy (strategy)
Policies define rules of rules for controlling communication and service behavior.
Port (port)
The endpoint or address unified resource locator (URL) of the message.
Port Type (port type)
See the service interface.
Process
See Business Processing.
Reference Data (Reference Data)
A combination of snapshot data used by the client.
SAGA (series record)
See Long-running transactions.
Service (service)
A software component, which is a message-driven behavior.
Service Agent (Service Agent)
One service, its main function is to help prepare to submit requests to other services and help explain the response of the service to the request.
Service fa? §ade (service interface)
The service interface opens the function of the system to the outside world.
Service Interface (Service Interface)
Definition of specific roles in the protocol.
Snapshot State (Snapshot Status)
A snapshot provides a restricted view on the status of a point in service. Snapshots are not necessarily the current state.
Stable Data (Stable Data)
Its meaning and explanation will not change the snapshot of the space and time.
STATEFUL Conversation (stateful session)
Communication between the parties must record all aspects of the previously exchanged data in this communication to subsequently perform meaningful exchange.
STATELESS Conversation (stateless session)
Communication between the parties, all messages in this communication can be interpreted independently; services do not need to remember previous requests and responses.
Transaction
All participants must agree with this unit, and a single work unit that works should be completed and can be completed.
Trust (trust)
Serving the reliability of other services and the trust of the information they provide.
User Interface Process (User Interface Processing)
A service, its main function is to integrate or coordinate the operations provided by the user interface service.
User Interface Service (User Interface Service)
Handle services with one or more people.
Go to the original English page
