I love the idea and I also agree that there is so much duplicated effort but the difficulty of making the "one service to rule them all" is that there is pressu

I love the idea and I also agree that there is so much duplicated effort but the difficulty of making the "one service to rule them all" is that there is pressure for it to be all things to all people, at which point, it becomes harder to use for a simple use-case. Take the crypto microservice. Someone says, e.g. "I notice that it doesn't support Argon2". If it doesn't, I can't use it, I would need to write my own library. Arguments ensue about you don't need Argon2 or "why not contribute the change to the library?". Maybe the maintainer doesn't want to accept the PR because they don't think the library needs it or they are not sure that the quality is high enough to accept. The library gets forked internally and the fork takes on a life of its own. I don't want to be negative but my experience is that people have a certain way of doing things and unless these services do it in that way, people won't live them. There are other ways in which they wouldn't be able to be reused like if people don't know how to build/deploy Go or they are only looking for something simple but the fully featured libraries are too hard to understand. Maybe having something is better than nothing but I think the saying is something like, "in trying to be all things to all people, you end up being nothing to any of them". I really hope I am wrong though because the amount of duplicate work in the world depresses me as an engineer!