3 ms·

I think it's a matter of scale, rather than quality - we obviously use languages and frameworks and patterns at Google.

• wwweston 11y ago
  Scale of operations at Google, or conceptual scale of the diagram? And if you feel like language and framework choice plays a significant enough role at Google that "stack" in the more traditional sense is something that's carefully considered by engineering, I'd love to hear about the details.
  • reagency 11y ago
    This diagram is about services that run o a machine and vend data to other machines, not the libraries or frameworks (GWT, etc) that implement the services. This diagram is more "zoomed out"
  • endtime 11y ago
    The scale of the diagram, though obviously a diagram of that scale can only be drawn for an organization with operations at that scale - so kind of both. I've mostly done backend/data stuff at Google, so I can't speak to traditional web dev decisions, but I've written design docs which discuss the tradeoffs between using Bigtable and Spanner, or Flume vs. Mapreduce, or one serving strategy vs. another, for some specific thing. Maybe those choices are vaguely analogous to choosing between Postgres or Mongo, nginx or Apache, etc. I imagine the guys who write webapps (not Search, obviously, but internal apps or things like our help pages) consider whether to use App Engine, Angular, Django, etc. on a per-app basis.