Existing data exchange solutions

Existing data exchange solutions

1. Rest Principles

   • Separation of Client and Server
     • Client and server work independently of each other, allowing for modification
   • Statelessness
     • The condition of either the client or the server does not matter to either party. By doing this, each message received is understood by both the server and the client, even when they are not aware of earlier messages. As a result, components can be controlled, updated, and reused without having an impact on the system as a whole, even when the system is in use. This promotes dependability, quick performance, and scalability.
   • Making Requests
     • Requires client to make request to server to retrieve or modify data
     • Request consists of:
       • HTTP verb
         • defines what kind of operation to perform
       • Header
         • allows client to pass along information about request path
       • path to a resource
       • optional message containing data
   • Communication between Client and Server
     • Servers respond to requests from clients to retrieve or modify resources.
   • HTTP Verbs
     • GET
       • Retrieve a resource
     • POST
       • Create a resource
     • PUT
       • Update a resource
     • DELETE
       • Remove a resource by id

2. Coding Environment

   • GraphQL
     • Query language
     • programming language and database agnostic
     • can specify exact data needed from API
   • Python
     • Emphasizes code readability with the use of significant indentation.
     • Easy to read
     • Vast library support
     • Portability
   • HTML
     • The standard markup language for documents designed to be displayed in a web browser.
     • HyperText Markup Language
   • CSS
     • language used for describing the presentation of a document written in a markup language
     • Cascading Style Sheets
     • Works well with HTML and javascript

3. Aspects

   • JSON
     • fast and easy to read due to compressed style
     • doesn't use start and end tags
     • allows use of arrays
   • XML
     • more secure than other options
     • allows more platforms for encoding
   • SOAP
     • Is a standard protocol
     • created so that different platforms can communicate
     • Built in compliance standards
       • security
       • atomicity
       • consistency
       • isolation
       • durability
   • Messaging
     • An asynchronous, decoupled form of inter-service communication in which senders of data place messages in a message queue until they are processed and deleted by receiving services.