4 ms·
This seems more complicated than just using the original APIs, as none of the sample applications or StackOverflow questions you might find with a quick Google
by jefflinwood 11y ago
This seems more complicated than just using the original APIs, as none of the sample applications or StackOverflow questions you might find with a quick Google (for instance, creating a capability token with Twilio) would apply any more.
As thinkingkong asked, what's the use case?
- kwrt 11y agoDid you try it? I think it makes it way easier if you need to integrate more than one API. But open for your opinions or suggestions how to improve it. The solution has just been launched, so yes there are not many tutorials out there. Use case is if you need to integrate more than one API in your app.
- jefflinwood 11y agoI was just trying to figure out what problem developers had that you were trying to solve. From your web site, it appears that your thesis is that (some) developers have a problem using multiple API's from multiple providers, and you are offering an integrated approach to make their lives easier.
- kwrt 11y agoThat's right. We've heard from developers that they spend over 50% of their development time for an ordanary app to integrate other services via APIs. CloudRail tries to reduce that significantly. 1 API (with some configuration) instead of N APIs for N services.