News for hackers. Stuff that matters.
Re:How We Built Our Stack for Shipping at Scale by ernestipark on Tuesday March 17, 2015 @02:22PM (#9220105)
As an engineer at HubSpot, I find our small team structure particularly empowering - though I'd be curious to hear of other orgs that run well with much larger teams as a counterpoint.
Re:How We Built Our Stack for Shipping at Scale by ing33k on Tuesday March 17, 2015 @02:51PM (#9220324)
Hi ! thanks for the sharing the post. just a quick question . was the architecture same from the beginning ? more specifically microservices ? or did you made a move from a monolithic application to this new architecture .
Re:How We Built Our Stack for Shipping at Scale by champion on Tuesday March 17, 2015 @03:02PM (#9220407)
I'm not sure how to best characterize it in the very beginning (and I wasn't there) but in the 3.5 years I've been here it has largely been smaller services -- even down to things like the app's nav is its own service. More recently I think we've really embraced microservices (the number of deployables has grown ~2x in the last year).

Personally I think after 5 (and definitely 10) engineers working on a single app I would look at whether you can break it down into independent services.

Re:How We Built Our Stack for Shipping at Scale by HenryTheHorse on Tuesday March 17, 2015 @04:14PM (#9221063)
Does not having a dedicated test/QA team affect productivity? How does this correlate with build quality in general?

Thanks,

Re:How We Built Our Stack for Shipping at Scale by champion on Tuesday March 17, 2015 @04:32PM (#9221213)
Personally I've been a fan as it aligns incentives for developers to care deeply about code quality/stability/etc. YMMV if not working on a SaaS product where build/deploy is measured in just a few minutes.

We've invested in a mix of both automated testing, of course, and a lot of monitoring/alerting/tracing to detect problems quickly. That can act as a safety net for deploying frequently that problems will be caught early and can be corrected (rollback or fix & roll-forward).

I'm a fan of saying we've chosen to optimize for MTTR instead of MTBF.

Re:How We Built Our Stack for Shipping at Scale by HenryTheHorse on Wednesday March 18, 2015 @04:58PM (#9228644)
Great answer. Thanks for the insight.
Re:How We Built Our Stack for Shipping at Scale by nahname on Tuesday March 17, 2015 @03:49PM (#9220821)
Roughly, how many dev teams are there at hubspot?
Re:How We Built Our Stack for Shipping at Scale by champion on Tuesday March 17, 2015 @04:27PM (#9221170)
About 25 plus or minus.
Re:How We Built Our Stack for Shipping at Scale by jnagro on Tuesday March 17, 2015 @05:05PM (#9221461)
teams are typically ~3 engineers, working with a Product Manager and a Product Designer
Re:How We Built Our Stack for Shipping at Scale by signal on Wednesday March 18, 2015 @08:25AM (#9224916)
This is super interesting! Are the product managers and designers a shared resource?
Re:How We Built Our Stack for Shipping at Scale by champion on Wednesday March 18, 2015 @10:28AM (#9225678)
PMs and designers work with one or more 3 person engineering team. Often times the PM/designer work across several engineering teams in 1 "family".