I love social software and interesting data.
I'm 28. I love cooking and trying new food.
I live in Brooklyn, NY Bayonne, NJ.
Contact me at david.lifson@gmail.com.
I'm the co-founder of Postling, a unified dashboard for small businesses.
It's important to me to give back to the startup community, so if you are interesting in hearing my thoughts about your startup, sign up for my office hours or send me an email.
My other sites:
The downside to using Apigee is that it introduces a latency into the whole system. Mulloy estimate sthat this latency is only 200 to 300 milliseconds, which is is acceptable for most apps, but starts to become noticeable for real-time apps like Twitter. For URL Shorteners, for example, 300 milliseconds can mean the difference between an acceptable and unacceptable lag. But that’s the price you pay for visibility into your APIs.
Apigee’s Ambition Is To Be The Google Analytics For APIs
What a ridiculous idea. Not only do you add a point of failure to your system that you can’t control (e.g. Apigee’s uptime), but you abuse your customers with 200-300 ms of latency for the privilege of doing so.
Also, there is nothing acceptable about 200-300 ms of latency for an internet app. I’d have serious doubts about anyone in this industry who doesn’t understand that.
