4 ms·

These solutions didn’t appear out of thin air because people get bored one day. Micro services solve tangible, real world problems. gRPC isn’t necessary hard t

• ioquatix 8y ago
  Improvements like...?
  • mping 8y ago
    Performance, I guess. Also, a schema. Eg json has schema but most apis I know don't use json schemas.
  • deleted 8y ago
    [deleted]
  • orf 8y ago
    Speed, schemas, code generation, built in backwards compatibility, extension points, public service definitions, introspection to name a few.
    • Thaxll 8y ago
      You forgot real bi-directional streaming but otherwise I agree :)
• sklivvz1971 8y ago
  > These solutions didn’t appear out of thin air because people get bored one day. I certainly did not say these architectures appeared out of thin air. They were invented to solve the problems of internet-scale companies. > Micro services solve tangible, real world problems. Incorrect. Microservices solve tangible, real-world problems when they are applied to the correct problems. Microservices might also create tangible, real-world problems whether they are applied correctly or not. In fact, that's one of the points of the article, if you read between the lines. > gRPC isn’t necessary hard to debug, and it brings a whole host of improvements over whatever ad-hoc mess you used before. I don't know what you are referring to. If your microservices are well done, good for you. You still need to optimize the transport, which is a cost you pay only because of your choice of architecture. If you used thicker services or a monolith you would have different problems, but not that one.