3 ms·

Why should serialization and deserialization be “effort”? Your data objects shouldn’t be more complex than is trivially represented with JSON or else you have a

• lmm 7y ago
  > Your data objects shouldn’t be more complex than is trivially represented with JSON or else you have a different problem. That's the whole problem I'm talking about. Like I said, it forces you to reduce all these interfaces to lowest common denominator. > Besides, while I’m not a microservices enthusiast, isolation isn’t the main goal of microservices, it’s being able to deploy, scale, and operate services independently from other teams. If you're just talking about each team having its own service, that's not what's usually meant by "microservices".
  • weberc2 7y ago
    > That's the whole problem I'm talking about. Like I said, it forces you to reduce all these interfaces to lowest common denominator. I don’t know what you mean by “lowest common denominator” or how “being forced to write good code” is inherently bad. There are lots of efficiencies to writing good code (easy to test, reuse, refactor, etc), not just writing microservices. > If you're just talking about each team having its own service, that's not what's usually meant by "microservices". That may not be the definition but it’s the principally cited advantage.