Choosing an adapter

The order to consider adapters in, and why the generic one is a LAST RESORT rather than a shortcut. FIRST: THE APPLICATION ADAPTER for that system, where one exists — the Fusion adapter, the adapter for a named SaaS product. It knows the system's catalogue, generates the structures for you, handles its authentication and its pagination, and understands its events. Using it is an afternoon; rebuilding that by hand is a week and it will be missing something. SECOND: THE TECHNOLOGY ADAPTER for the protocol — FTP, database, JMS. Where there is no application adapter but there is a well-defined transport, this is the right level: it handles the mechanics without pretending to understand the business object. LAST: REST OR SOAP AS A GENERIC CALL. Anything can be reached this way, which is exactly why it is tempting and exactly why it is last. WHY THE GENERIC ONE IS A…

In this module: Module 3 · Connections and adapters

1. 1What a connection is
2. 2Choosing an adapterFree preview
3. 3The REST adapter
4. 4The SOAP adapter
5. 5The FTP adapter
6. 6The database adapter
7. 7Testing a connection properly
8. 8One connection or several
9. 9Connectivity agents, and when you need one
10. 10What breaks: four connection failures
11. 11Lab briefing · Three connections, three systems