Re:Apply HN: Brightwork – Making APIs More Intelligent
by palakchokshi on Wednesday April 06, 2016 @06:54PM
(#11442953)
Another great use case is Analytics. On a recent project we started out using Facebook Analytics, switched to Google (code change everywhere) then wanted to move to MixPanel (again lot of code change). Would be great if there was a single API that allowed me to change the backend API seamlessly. Essentially an abstraction layer.
[ Parent
| on HN ]
Re:Apply HN: Brightwork – Making APIs More Intelligent
by josh_carterPDX on Wednesday April 06, 2016 @07:03PM
(#11443037)
Yeah we've heard this as a big painpoint as well. We will be offering some basic usage information ourselves that we can abstract, but it would be good to be able to give more flexibility here. Definitely on our roadmap!
Re:Apply HN: Brightwork – Making APIs More Intelligent
by AkiraMichi on Wednesday April 06, 2016 @07:19PM
(#11443148)
Wouldn't it make more sense to abstract away the analytics code in your app and write it as an independent entity and then just implement an entity gateway for all the providers you want to support?
Re:Apply HN: Brightwork – Making APIs More Intelligent
by palakchokshi on Thursday April 07, 2016 @01:08AM
(#11444863)
You can abstract in your code using a Provider pattern but if this product can provide it out of the box along with the other features I wouldn't spend time on coding the Abstraction.