4 ms·
Show HN: CloudRail – API Integration Solution
- vittore 10y agoDiscovered it couple of weeks ago myself too. Anyone does have any experience with it?
- cloudrail 10y agoTons of experience (CloudRail team here) :-) Happy to answer any questions you might have.
- vittore 10y agoThanks! Any plans on supporting SparkPost for emails?
- cloudrail 10y agoNot yet, but it's a good suggestion. I'll bring that up in the team. Thanks
- erik_p 10y agoAny plans to add reddit's API under the social category?
- cloudrail 10y agoAlso a good suggestion. We'll check if thats possible. Thanks!
- cloudrail 10y agoWow, thanks for the post @gro_us. CloudRail team here... happy to answer any questions.
- gro_us 10y agoAlready using it. Great tool, thanks
- Mandatum 10y agoThe biggest risk I see with using your API vs implementing a native API is the native API's are unlikely to shutdown in the next few years. It seems very risky from my perspective to use a third-party API which may go down leaving me to switch to native API when its library is no longer updated, totally defeating it's intended purpose. Do you plan to open source the code if your company shuts down? (from asimuvPR when Brightwork.io tried to do the same thing, but ultimately ended up pivoting) 1) What APIs has your team built before that qualifies them to build this? 2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you? .. 4) What language will the API be written in? 5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens?
- cloudrail 10y agoGood question, thanks. You are right, in case CloudRail goes down no one will maintain the libraries anymore. Despite the fact that we won't go down :), you have to ask yourself if the risk is really that big? The service definitely saves you time now and for the next X years. How many time would you invest during that period with native integrations? Definitely one by one SDKs to integrate and I bet some of them need to be replaced as well. E.g. Dropbox from v1 to v2 was a complete new API and SDK. I think integrations need to be maintained anyway and in the worst case (CloudRail goes down) you have to invest max the same time compared to manual. We love open source and this is an option as well. 1) What APIs has your team built before that qualifies them to build this? Our team has been in the API business for 4 years now with a lot of different projects and products. 2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you? We have a system called API Change Management. Every connected API is monitored for changes. Once something happens or is announced we update our SDKs and put that information back in the system. Afterwards the system checks all SDKs which are implemented by customers and which integrations they use and automatically notify affected ones by email and via our portal. .. 4) What language will the API be written in? Currently we support Node.js, Android, Java and iOS (Swift & Objective-C) 5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens? We let customers use their own API credentials which they get directly from the providers.
- jitl 10y agoThis reminds me of Kloudless: https://kloudless.com/ https://kloudless.com/ It's interesting though that CloudRail is library-only; I like that you don't need to worry about CloudRail uptime. However, doesn't this mean I need to upgrade my dependency when a downstream API changes? With Kloudless or other gateways, the gateway can update independently of my application, so the strategy is a trade off
- cloudrail 10y agoYou are right, in the end it is a trade off. CloudRail has no down times, can't touch your data and is as performant as a native implementation. But yes, in case of an API change you have to update the SDK. We have a notification system though. You will get an email if you are affected by a change.
- cloudrail 10y agoYou'll get a way better overview on the landing page https://cloudrail.com https://cloudrail.com. The page which was linked here provides actually more details.
- gro_us 10y agoFAQ via email: Yes we are working on a .NET SDK and will release it in the next months. If you sign up for a free account, we'll keep you in the loop.
- aeharding 10y agoDoes this break anyone else's two-finder navigate back gesture on Mac w/ Chrome after scrolling down in the page?
- cloudrail 10y agoJust tested it and you are right. Don't ask me why, works with Safari. We'll fix that.
- deleted 10y ago[deleted]