Thanks Chandan, we're hearing this loud and clear. Open to give us feedback on pricing/packaging changes we're working on? If you're willing, can you send me an email at: ilya @segment.com
Thanks for your feedback, "painful" is not what I like to hear. If you're willing, will you send me an email ilya @segment.com, would love to get details.
Hey, just wanted to let you know that we're reading/listening and this is really helpful feedback. I'd love to do a phone call, and get your feedback on a few pricing/packaging changes we're working on. If you're willing, my email is ilya @segment.com
Hey, wanted to say that I really appreciate the feedback and we're releasing this program exactly to address it. This is Ilya, one of the co-founders of Segment.
Re: how the program works on the backend — For new startups (<2 years, <$5M raised), the Startup Program provides $25k of annual credit (and $50k credit if you're applying thru an accelerator) on the team plan which makes "Segment Free" for 99% of the thousands of startups that use Segment. You can apply for it for multiple years, and after you graduate, we'll provide graduated discounts off our standard plans (50% in year 1). This is designed to be affordable for the entire time that a startup is getting off the ground.
Re: value over time — we see companies of 2+ years of age use an average of 7 source types (web, mobile, crm, stripe, ..) and 8 destination types (google analytics, event analytics tool, data warehouse, email marketing tool, A/B testing tool, ..) accounting for 56 point to point integrations. Each source <> destination connection takes an average of 24 hours to do initial API integration and more beyond to maintain, so hours can add up. (https://segment.com/academy/choosing-stack/how-stacks-evolve...)
We're also buffering data behind the scenes with Centrifuge when partner APIs have a downtime event to get your data deliverability as high as possible :) (https://segment.com/blog/introducing-centrifuge/)
Either way — this feedback is super helpful, and if you'd like to chat more I'm ilya@ segment.com. Thanks!
Hey, this is Ilya - i'm one of the co-founders and original author of the .NET library - I'm really sorry that happened. In the early days, I was the author of 5 of our open source libraries and also a student of the .NET platform.
Today we have a larger team working on our libraries - .NET in particular has 200+ customers (mostly on our business tier) and we're processing 21B+ API calls/mo originating from .NET. If you could send me an email at [email protected], I'd love to chat live and collect any other feedback you have from the experience. Thanks again for leaving the note.
We used the original Firebase database product to build http://socrates.io/ 3.5 years ago, and I remember getting Socrates running in a few hours. I’m looking forward to seeing them up the bar on speed of development / ease for their next 10 products :) Nice work team!
Segment is an analytics API that helps businesses integrate their entire analytics stack. Once customers send us data, we can send it to 180+ other integrations and databases like Redshift.
We write code in Go and Node, process tens of billions of events a month, and contribute heavily to open source:
Regarding immigration: I don't know if there was much selection bias as we were in the immigration queue for 10 years before being selected. The Anti-Defamation League told Bill Clinton that the situation in Russia was getting worse (1996), and he increased the annual quota of Russian Jews allowed to enter the US.
Regarding the second point: we have no more relatives in Russia, so the narrative is not meant to help anyone immigrate to the US.
As far as the story goes that Russians were equally discriminated against, and it was a case of bribery, you can take a look at my comment below of more family examples. Or you take a look at this list of Math problems that were specifically given to Jews during their admission exams into Moscow State University: http://arxiv.org/abs/1110.1556 . Thanks to @Prognosticus for sending me the link!
Author here. As far as I understand, the Jewish quotas were not proportional to the population.
The other significant difference is that all these policies were completely opaque, not like you can find out how much Jews the university can accept this year. Officially, no such policy existed, but everyone knew it did.
In my dad's case, he was told he failed the health exam, which was a complete lie.
There were many other cases in my family where a similar thing happened:
- Besides having a passing score, my grandmother was not accepted into a tech university, while her Russian friend with the exact same grade was.
- Another one of her friends disappeared (taken to a political prison camp), after she publicly complained that she wasn't accepted into her desired university because of religion.
- my mom wanted to be a teacher, but had been told by her neighbor (who worked as a professor) to not even try applying to the Pedagogical University of St. Petersburg, as they flat out didn't accept Jews.
- post graduation, my dad wanted to work at a high-tech Moscow university lab. Back then, you were assigned to a job after graduation based on your grades. The Moscow lab was reserved for the top of the class (and my dad was in the top 5%). However, during the assignment committee, the director repeated "David Vladimirovich" twice. This was a common Jewish name, and he made sure that everyone knew it. The committee decided that my dad was to go work in a lab in Ufa (2000 km away - http://goo.gl/maps/a342A). Far places like that were reserved for lower placing students. When my dad asked why he didn't place into the Moscow lab, they told him, "we're the ones that ask the questions here."
the main idea is ease of integration. the developer doesn't have to write code to queue and dequeue, and the sys admin doesn't have to set up and support a queuing system. it's just a drop-in install.
regarding the impact on application performance, each of the libraries has a maxQueueSize feature which stops accepting messages into the internal queue if the flushing can't keep up. you can check out how maxQueueSize works in our docs: https://segment.io/docs
server-side events are best used in conjunction with the client-side libraries (via analytics.js). For example, you can use analytics.js to load the GoSquared javascript library to keep track of referrers / concurrents on the page, etc. Then you can turn on Mixpanel to keep track of events that happen server-side, such as "Payment Processed", etc ..