zubairov

10 ms·

61.
Show HN: User innovation with APIs(blog.elastic.io)
6 points by zubairov 14y ago|1 comments
62.
How to promote APIs?(blog.elastic.io)
1 points by zubairov 14y ago|0 comments
63.
Show HN: Open Source business models(zubairov.posterous.com)
2 points by zubairov 14y ago|1 comments
64.
Ask HN: What are distribution channels do you use for your API?
1 points by zubairov 14y ago|0 comments
65.
Show HN: How we integrate Dropbox(elastic.io)
1 points by zubairov 14y ago|0 comments
66.
by zubairov 14y ago
Thanks Tom! As we switched from Java to JavaScript it gave us incredible boost in productivity. And also staying on the shoulders of giants like node.js, twitter bootstrap speed things up allot.
67.
Rate my startup: Yahoo! Pipes on steroids(elastic.io)
2 points by zubairov 14y ago|2 comments
68.
by zubairov 14y ago
Exactly! We are Yahoo pipes on steroids.
69.
by zubairov 14y ago
Good points are covered in this blog post, however what if we would push it even further? Why would people need to download a package? Why would anybody need to learn a programming language you package designed for (or assume you distribute
70.
Ask HN: How do you integrate SaaS applications used by your company?
1 points by zubairov 14y ago|0 comments
71.
by zubairov 14y ago
Yes. Good point. It's indeed quite expensive to do the graphic generation on the server. We use a caching from Amazon CloudFront. They have a great feature 'custom origin'. We just put our heroku server URL as an origin for CloudFront and c
72.
Show HN: Reusing browser JavaScript code on server(blog.elastic.io)
7 points by zubairov 14y ago|3 comments
73.
by zubairov 14y ago
Awesome tool. I really like how you integrated the component functionality into the UI, so that you could select a particular form from Wufoo or list the Salesforce object. What components do you have right now and what are planned for the
74.
YCombinator German clone funding YCombinator Startups clones(zkombinator.com)
10 points by zubairov 14y ago|6 comments
75.
by zubairov 14y ago
Hi, No 1005 ms was not a cache miss it was a request to the origin server. Latency was 799 ms. I assume CloudFront will contribute some latency, however in our case (we are using Heroku) our servers were already on Amazon platform, therefor
76.
by zubairov 14y ago
Good question. It depends on the caching strategy. As we essentially serve Gists we have two types of URLs one something like [gist-id]/ meaning the latest version of that particular gist and another URL is [gist-id]/[revision-id] which is
77.
Show HN: AWS CloudFront (CDN) for dynamically generated content(blog.elastic.io)
15 points by zubairov 14y ago|8 comments
78.
by zubairov 14y ago
Hi You can try http://elastic.io We are in private beta and still missing some of the components but it can be fixed rather quickly. Sign up for beta access and drop us a line on info at elastic.io Renat
79.
by zubairov 14y ago
Hi, Nice one. What about using other data sources? What geo-coding is used in this sample?
80.
Track clicks on links in your tweets(blog.elastic.io)
2 points by zubairov 14y ago|0 comments
81.
by zubairov 14y ago
Right. With HN in our samples users need to do an additional hop over to the main website. I think next time we could compare it on the other HN link.
82.
by zubairov 14y ago
Hi Andreas, We don't have yet any data about this. We are in private beta phase so we just got started. We track our visitors/users very carefully, so by the time goes by we will definitely see some numbers that we can share with HN and Bet
83.
Show HN: Our startup got featured on HN and BetaList: Statistics, comparison.(blog.elastic.io)
32 points by zubairov 14y ago|12 comments
84.
API billing surprises and how to avoid them(blog.elastic.io)
1 points by zubairov 14y ago|0 comments
85.
by zubairov 14y ago
Great idea! We also thought about this one. As we will re-sell cloud APIs it will be definitely a good feature to protect our users from slashdot effects.
86.
by zubairov 14y ago
Yes, that's definitely a problem. For our use-case where we want to follow SW engineering best practices like versioning, continuous integration, etc. we thought reuse of git as a repository and them to user will be a good thing.
87.
by zubairov 14y ago
Thnx for your feedback. Very good point! We will definitely improve our website in the nearest future.
88.
by zubairov 14y ago
Exactly. Primary motivation was to have a simple versioning for user data flow and Git repository management overhead was too much, however after we implemented it we realized that data portability is a by-product of that.
89.
by zubairov 14y ago
Agree. Also with our current implementation right now we might pose a bit too much load on Gists (which is actually only our fault), however it's only first step. We want to give our users their data at hand, I could imagine a potential ind
90.
by zubairov 14y ago
Thnx for your comments Jason. Indeed any 3-rd party sign-in module lower down the conversion, however, on a given stage it's intentional. We would like to speak out to developers, and to those who are familiar with basic principles of open

More ›