Open Architecture

Recommendations

Info

ADAM Software Technical Proposition: Open Architecture How the ADAM Platform Delivers Exceptional Flexibility Throughout its history, ADAM Software (ADAM) has been focused on developing software applications (the ADAM Platform) that support mission-critical processes in large global enterprises. ADAM has also long recognized that most enterprise customers will want or need to integrate the ADAM Platform with other marketing software applications and/or other enterprise information systems, and to modify or extend the functionality of the ADAM Platform to meet their specific needs. Therefore, the ADAM Platform has been engineered from the ground up to have an open architecture that provides an exceptional level of flexibility and interoperability. The flexibility of the ADAM Platform is derived from two key mechanisms: º ADAM provides two robust and fully-documented application programming interfaces that enable access to all of the functionality of the ADAM Platform. º All components of the ADAM Platform have been developed using the Microsoft .NET framework and make extensive use of the provider model design pattern. ADAM Software NV adamsoftware.net info@adamsoftware.net 5
ADAM Software Technical Proposition: Open Architecture The ADAM REST API In early 2016, ADAM introduced an application programming interface for the ADAM Platform (the ADAM REST API) that is fully REST-compliant. A “RESTful” API leverages the HTTP software protocol to enable the integration of software systems in a more standard and easy-to-understand way. The ADAM REST API facilitates the integration of the ADAM Platform with other software applications in three significant ways: º It eliminates the need for detailed knowledge regarding the language and architecture of (a) the ADAM Platform, and (b) the software applications with which the Platform will be integrated. º It allows for a “loose coupling” between the ADAM Platform and other software systems, which makes it easier to maintain integrations over time. º It allows full control over who can connect with the ADAM Platform and what can be passed between the Platform and another software application. The ADAM REST API supports two ways of consuming and navigating the API: º HAL/JSON hypermedia—Once a resource in the ADAM Platform is retrieved, a user’s client can bookmark the URI in its cache. The existing relation names will not change over time, but new relations can be introduced. Links in the returned resource representation help the user to navigate the ADAM REST API just by following those links. Using this approach helps create API clients/servers that do not depend too much on each other and can be developed in an independent way, as long as both the client and the server have a common understanding of media types used in the communication. For example, an enterprise user can start using the ADAM REST API by going to the root URI of the API and discover all the accessible resources. From that point on, the user can follow links and explore the resources existing throughout the ADAM REST API. Then the user can use the “select” keys, present in most of the resources, which provide information about which sub-resources can be embedded in that resource. This way, the user can retrieve the exact information needed in a single request, which helps optimize the “chattiness” of the API for a specific use case. º Plain JSON consumption—In addition to using HAL/JSON hypermedia to interact with the ADAM REST API, clients can also consume the API using plain JSON. This is a simpler but less robust approach, since it lacks discoverability and requires upfront knowledge of the URI’s for all the endpoints that the client will need. For pure JSON clients, ADAM provides an exhaustive collection of the endpoints available in the ADAM REST API. The ADAM REST API is fully documented via a reference manual that contains a complete and detailed explanation of the API’s functionality. ADAM Software NV adamsoftware.net info@adamsoftware.net 6
Page 1 and 2: Technical Proposition Open Architec
Page 3 and 4: ADAM Software Technical Proposition
Page 7: ADAM Software Technical Proposition
Page 19: ADAM Software Technical Proposition

Open Architecture

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?