When Creating APIs, Focus your API Gateway on What it Does Best by Robert Wunderlich
January 4, 2018 Leave a comment
When talking with customers and prospects, I often hear about two requirements; converting REST to SOAP or SOAP to REST and Caching of data for performance.
These are great opportunities for an API Gateway, but should be used with extreme caution. Misuse of either of these features can cause performance problems in your gateway or even worse, putting your sensitive data at risk!
Using an Integration Platform with an API Platform provides the opportunity to follow some best-practice approaches to data isolation as well as scaling of certain heavy-weight operations. Furthermore, by separating these concerns, sensitive data is better protected
First, let’s look at the key purposes of an API Platform and an Integration Platform. The API Platform is responsible for the following: Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Forum
Wiki
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress
About Jürgen Kress
