> People view SRE in many difference ways. If you were to go through the Google SRE book, there's nothing explicit in there about building "platform" or doing a

> People view SRE in many difference ways. If you were to go through the Google SRE book, there's nothing explicit in there about building "platform" or doing any infrastructure engineering. In a past life I worked on an SRE team that backed up data to cassette tapes using a fleet of robots with lasers. https://youtu.be/kQ2taAttvwo https://youtu.be/kQ2taAttvwo That was easy. Hard SRE work is more like Traffic Team. My personal view is that microservices, libraries, frameworks, apis, abis, etc. have a great deal in common today with how we've always thought about internet routers. Ask yourself this: if JavaScript web apps could run traceroute, then how many stakeholders do you think would show up before your query even reaches the wire? So I think what the author Nick is saying makes perfect sense. Yes, these platform layers can cause difficulties. Can we fix them? Yes, just read the SRE book. That same wisdom will carry over just fine to this kind of problem.