Hacker Newsnew | past | comments | ask | show | jobs | submit | f2prateek's commentslogin

Congrats on the launch!


Most of these libraries are open source. One we had the most friction updating was was our library that wraps common logic for dealing with user generated events - https://github.com/segmentio/facade (this is the example that was referenced in the blog post).


At the time we did the split, we had <30 destinations and 3-4 engineers working on this system. At the time we decided to merge, we had > 140 destinations with ~8 engineers, of which roughly 3 full-time engineers spending most of their time just keeping the system alive.


How much of the code was shared among these services? It sounds like you essentially had mostly the same code running in 140 different configurations with only some translation logic and glue varying between each. I'm not surprised you found this untenable. This is akin to running a microservice per web page.


We wrote about how we analyzed our AWS usage https://segment.com/blog/spotting-a-million-dollars-in-your-..., and then some of optimizations we made to cut down costs https://segment.com/blog/the-million-dollar-eng-problem/.


This is an awesome breakdown!


Assuming this app uses the Segment SDK, the SDKs are open source and you can see the implementation details yourself, e.g. https://github.com/segmentio/analytics-android. There's a high level overview at https://segment.com/blog/lifecycle-of-a-mobile-message.


There is some good research already on how page load times can impact conversions.

https://www.quora.com/How-do-page-load-times-affect-e-commer...


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: