3 ms·

Google runs practically everything internally as services. Nothing about the code repository makes it impossible to run microservices. Where did you get the ide

• kuschku 11y ago
  The article claimed the code, and they way it's run, is a monolithically developed and deployed product. If that’s not the case, I apologize for misunderstanding it. But if it was the case, I wanted to state that it might not be wise, for the same reasons as this thread mentioned https://news.ycombinator.com/item?id=10195423 https://news.ycombinator.com/item?id=10195423 EDIT: Thanks for telling me, though! Always nice to be proven wrong, as at least I learnt something today :D
  • Filligree 11y ago
    It's not the case. You should think of Piper as a single filesystem which permits atomic multi-file edits. And that's about it; there's nothing in that which forces any particular release structure on you.
  • spectral321 11y ago
    The talk did mention (briefly) that monolithic codebase and monolithic binaries/software aren't strictly related. It's likely that monolithic software is easier in a monolithic codebase, but I don't think that microservices are harder in a monolithic codebase. Yes, we tend to statically link, but that's for library dependencies (i.e. things like the protocol buffers libraries/definitions). I don't work at all in this area, so this is a guess, but I imagine that it's extremely rare for unrelated teams to have application logic linked into the same binary - just making a release would involve coordination from so many teams :)