Simple vs. Rich APIs


Cloud Interoperability with Rich APIs

JNBridgePro enables you to take APIs in both cloud-based and ground-based applications and make them available to both .NET-based and Java-based consumers. You can then package up the API access stubs and make them downloadable, so other in-the-cloud or on-the-ground applications can consume them.

Simple APIs

SOAP-based and REST-based web APIs are designed to return simple values — strings, primitives, and collections of strings and primitives — while they can return more complex objects, they're generally best suited for basic data.

Web-based approaches to APIs are generally stateless, so each request is treated as unrelated to any previous request. These APIs do not permit stateful interaction or asynchronous notification.

While some of the characteristics of simple APIs may be considered a virtue — the interfaces are simple, so it's easy to implement calls; they're loosely coupled, so state isn't generally an issue — these same characteristics can sometimes cause problems.

Not all useful APIs are REST-based: existing software may have to be extensively and expensively re-architected to give it a REST-based interface. Even when re-architecting is practical, deep functionality may be lost. This deep functionality can include many programming features, including object orientation, asynchronous notification, and statefulness, which are useful in the cloud as well as on the ground.

Rich APIs

JNBridgePro provides high-performance API integration that allows you to access your complete set of rich APIs. It allows any API implemented in Java or .NET to be exposed to the outside world, and consumed by some other Java or .NET application.

Rich APIs generated with JNBridgePro provide full support for:

  • Asynchronous communications
  • Callback notifications
  • Remote references
  • Maintain state
  • Transactions
  • GUI embedding
  • Full access to objects, components and libraries

JNBridgePro is "API integration for the rest of us."