While SOLID has always been the standard, it can sometimes be difficult to always apply its principles, and according to Dan North, it may even be outdated.
Managing the requirements of GDPR compliance is easier said than done. Mehdi Medjaoui shares some advice on how to facilitate GDPR compliance through APIs.
In this episode of Cocktails, we talk to a distinguished university professor on cybersecurity and touch on some taxonomies and frameworks for organizations to build their security.
In this use case we will accept a payload via HTTP, inspect the header of the request and then depending on the value in the header, write the payload to a SQL database.
Do you want to take the response from a RESTful API and write it to an SQL database? Here, we'll sync billing data from our Demo Billing API to an SQL database.
Thanks for the question Oliver. TORO provides an integration framework that enables a user to create integration services automatically from an API schema such as OpenAPI or Swagger (amongst others). You then just drag n drop the API services into your own integration service logic. No coding required from end to end. Note, however, that TORO Integrate is an enterprise-class solution that enables full customization of service logic as required.
Good point Frank. It is the responsibility of the API publisher to provide an SDK and keep it updated with API changes. If you are getting that from over 70 publishers then you are doing well. In our experience, most API publishers provide some form of documentation but not all provide an SDK and of those that do they don't necessarily keep it up to date with their latest changes. Can be even worse if the SDK is provided by a third party.
The only way that the services for an API would not be updated is if the publisher didn't release an updated API schema. Or if you are using a tool like TORO Docs to OpenAPI then you just re-execute the crawl strategy of the API documentation and automatically generate a new API schema. Either way, you have a new API schema to now machine generate your services and away you go...
We have implemented thousands of APIs and can tell you that many companies (including some very large saas companies) that do not apply the same strict versioning/backward compatibility strategies that you do. Even if an API update was backward compatible you would still need to recode your connector if you wanted to take advantage of whatever new features that API update contained. That means dragging the code base for that connector out of source control, have a developer read through the code base to understand how it has been implemented, update it, test that the changes have not broken anything, build, deploy etc etc.
Glad to hear your migration went well Frank. Whilst true that a connector will abstract the implementation of an API the fact remains that when the API changes the connector will need to be rewritten. Writing code takes time and is prone to error. The advantage of using an API schema to machine generate the services for an API is that this can be done extremely quickly and by any developer - even those not familiar with the project. BTW, whilst TORO Integrate is a proprietary platform (as are OSB and Redhat Fuse) OpenAPi is an industry alliance of the top players in the industry and is part of the Linux Foundation.
CORE
Comments
May 06, 2019 · David Brown
Thanks for the question Oliver. TORO provides an integration framework that enables a user to create integration services automatically from an API schema such as OpenAPI or Swagger (amongst others). You then just drag n drop the API services into your own integration service logic. No coding required from end to end. Note, however, that TORO Integrate is an enterprise-class solution that enables full customization of service logic as required.
May 06, 2019 · David Brown
Good point Frank. It is the responsibility of the API publisher to provide an SDK and keep it updated with API changes. If you are getting that from over 70 publishers then you are doing well. In our experience, most API publishers provide some form of documentation but not all provide an SDK and of those that do they don't necessarily keep it up to date with their latest changes. Can be even worse if the SDK is provided by a third party.
May 06, 2019 · David Brown
The only way that the services for an API would not be updated is if the publisher didn't release an updated API schema. Or if you are using a tool like TORO Docs to OpenAPI then you just re-execute the crawl strategy of the API documentation and automatically generate a new API schema. Either way, you have a new API schema to now machine generate your services and away you go...
May 06, 2019 · David Brown
Couldn't have said it better myself Robert
May 06, 2019 · David Brown
We have implemented thousands of APIs and can tell you that many companies (including some very large saas companies) that do not apply the same strict versioning/backward compatibility strategies that you do. Even if an API update was backward compatible you would still need to recode your connector if you wanted to take advantage of whatever new features that API update contained. That means dragging the code base for that connector out of source control, have a developer read through the code base to understand how it has been implemented, update it, test that the changes have not broken anything, build, deploy etc etc.
May 06, 2019 · David Brown
Glad to hear your migration went well Frank. Whilst true that a connector will abstract the implementation of an API the fact remains that when the API changes the connector will need to be rewritten. Writing code takes time and is prone to error. The advantage of using an API schema to machine generate the services for an API is that this can be done extremely quickly and by any developer - even those not familiar with the project. BTW, whilst TORO Integrate is a proprietary platform (as are OSB and Redhat Fuse) OpenAPi is an industry alliance of the top players in the industry and is part of the Linux Foundation.