Overview¶
Description¶
TransactionDb rest server provides an easier way to access the remote transaction database to get transaction counts.
REST Design Goals¶
The REST design provides the following:
- Performance between component interactions, which is important for user-perceived performance and network efficiency;
- Scalability allowing to support large numbers of components and interactions among components;
- Simplicity of a uniform interface;
- Modifiability of components to meet changing needs;
- Visibility of communication between components by service agents;
- Portability of components by moving program code with the data;
- Reliability in the resistance to failure at the system level;
Client–server architecture - The client–server provides the separation of concerns.
Statelessness - The client–server communication is constrained by no client context being stored on the server between requests. Each request from any client contains all the information necessary to service the request, and session state is held in the client.
Layered system - A client cannot ordinarily tell whether it is connected directly to the end server, or to an intermediary along the way. Intermediary servers can improve system scalability by enabling load balancing and by providing shared caches.
Uniform interface - The RESTful design decouples the different components of the system.
Security¶
Transaction Rest server supports TLS 1.2
Instructions on how to enable TLS can be found in section 6.1.