Snap is laying off about 100 engineers

Re:Snap is laying off about 100 engineers by jxub on Wednesday March 07, 2018 @04:38PM (#16540150)

Is there an example of a million-user/big B2B company built entirely on top of FAAS like AWS Lambda and some lind of database with auto scaling, sharding et al. (maybe Spanner or CockroachDB [0])? I suspect once somethink like that happens we could have companies that have almost Google scale while just employing a couple of engineers.

[0] As a side note, I'm sure a blueprint for handling the common DB scaling problem. I suppose we could train a ML model to read some logs/usage stats and handle the remainder of edge cases. But making such a model will probably require hundreds of engineers so I guess we're safe at the moment.

[ Parent | on HN ]

Re:Snap is laying off about 100 engineers by eitally on Wednesday March 07, 2018 @04:57PM (#16540308)

The scaling isn't the problem that requires large engineering teams. It's partner integrations, compliance work, and all sorts of things that are extremely non-core.

[ Parent | on HN ]

Re:Snap is laying off about 100 engineers by warrenm on Monday March 12, 2018 @12:45PM (#16569401)

this 100x!

[ Parent | on HN ]

Re:Snap is laying off about 100 engineers by askafriend on Wednesday March 07, 2018 @07:14PM (#16541192)

Snapchat and Nextdoor are great examples. The former runs most infra on Google App Engine, and the latter runs primarily on AWS.

[ Parent | on HN ]

Re:Snap is laying off about 100 engineers by simonw on Wednesday March 07, 2018 @06:33PM (#16540990)

Snapchat was built on Google App Engine, so they're probably one of the best large scale examples of this.

[ Parent | on HN ]

Re:Snap is laying off about 100 engineers by stickfigure on Wednesday March 07, 2018 @08:47PM (#16541621)

This is true, and really one of the more mysterious things about the headcount. This should be an example of how to keep an organization lean as it scales. I wonder why it isn't.

[ Parent | on HN ]