Literature Flashcards
system integration =
the process of enabling different systems, technologies or application to communicate, interact, and work together seamlessly
application integration
- Electronic Data Interchange (EDI)
- Remote Procedure Calls (RPC)
- Common object request broker architecture (CORBA)
- simple object access protocol (SOAP)
- REST
- GraphQL
application server =
a dedicated software component in a three-tier or multi-tier architecture which provides application logic (business logic) and which allows for the separaten of application logic from user interface functionality (client layer), delivery of data (Web server), and data management (database server)
functions of an application server:
- providing application logic
- separation of concerns
- middleware services
- transactional guarantees
- scalability and load balancing
- support for SOA
REST API (aka REST web services) =
a software architectural style that deverlopers apply to web APIs.
REST API (aka REST web services), strengths:
- easy to integrate with due to small learning curve
- Use of http so there are no expensive tools required to interact with the web service
- Scalable, efficient and fast duet o smaller message formats and no extensive processing.
REST API (aka REST web services), weaknesses:
- lack of security
- Inability to maintain state, maintaining state lies on the client which can make the application heavy.
SOAP API (aka WS-* web services) =
a message specification for exchanging information between systems and applications.
SOAP API (aka WS-* web services), strengths:
- A dependable way to define and operate APIs across an enterprise at scale, and is the backbone applications and integrations that said enterprise depends upon
- Standardised
- Pre-built extensibility
- Built-in error handling
SOAP API (aka WS-* web services), weaknesses:
- SOAP can make it slower to evolve and iterate on APIs
- Longer to onboard new developers who are not familiar with SOAPs older methods
- SOAP uses XML for all messages
GraphQL web services =
a query language that lets developers construct requests that pull data from multiple data sources in a single API call. gives clients exactly what they request from a GraphQL server and no more.
GraphQL web services, strengths:
- It is efficient so there is no under or over-fetching
- GraphQL has the ability to retrieve many resources in a single request saving time and bandwith
- Allows for precise querying when working with large APIs that return lots of data
- Good for complex systems
- Fast process
GraphQL web services, weaknesses:
- Lack of built-in chaning support
- Performance issues depending on the complexity of the query
- Due to its complexity, it can take a long time to fully understand
HL7 V2
H
HL7 V3 & CDA
HL7 FHIR
DICOM