4 ms·

Microservices can't have dependencies between each other otherwise they aren't microservices. I think the main issue is just the other engineers you are workin

Microservices can't have dependencies between each other otherwise they aren't microservices. I think the main issue is just the other engineers you are working with. If they are bad, they will screw anything up.

okr 4y ago
How would you design a microservice, that does not depend on another?
- tangjurine 4y ago
  Microservice 1 <-> on call engineer copy pasting <-> Microservice 2
- williamcotton 4y ago
  Send a JSON package with some HTML and dimensions, get back a JSON package with links to that HTML rendered as JPEGs at the requested dimensions.
  - sseagull 4y ago
    At some point you are going to have another service that uses this HTML->JPEG service though. That would be a dependency, at least in my view (ie, if the HTML->JPEG service goes down, something else will break). Or are all microservices user facing?
Ygg2 4y ago
> Microservices can't have dependencies between each other otherwise they aren't microservices. See Hyrum's law: Put succinctly, the observation is this: With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody. One example we bumped spring from 2.1->2.4 (not actual version numbers) Harmless, no? What's worst that can happen? Failure when doing some but not all operations. Why? Because some Python/Java micro-services down the operation chain expected null fields to be omitted and the default behavior was changed (between Spring versions) to write null fields instead. Which only occurred on those services that relied on null fields being omitted. Fix was easy but finding the bug was difficult.
kubanczyk 4y ago
Microservice is a module. A module that got separated by a network layer, most often due to somebody's momentary lapse of judgement. It's encouraging that you forbid the next person to fall into identical trap (you effectively say: this kind of remote module must not use further remote modules). Alas... they can, and they will.

okr 4y ago

How would you design a microservice, that does not depend on another?

tangjurine 4y ago
Microservice 1 <-> on call engineer copy pasting <-> Microservice 2
williamcotton 4y ago
Send a JSON package with some HTML and dimensions, get back a JSON package with links to that HTML rendered as JPEGs at the requested dimensions.
- sseagull 4y ago
  At some point you are going to have another service that uses this HTML->JPEG service though. That would be a dependency, at least in my view (ie, if the HTML->JPEG service goes down, something else will break). Or are all microservices user facing?

Ygg2 4y ago

> Microservices can't have dependencies between each other otherwise they aren't microservices. See Hyrum's law: Put succinctly, the observation is this: With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody. One example we bumped spring from 2.1->2.4 (not actual version numbers) Harmless, no? What's worst that can happen? Failure when doing some but not all operations. Why? Because some Python/Java micro-services down the operation chain expected null fields to be omitted and the default behavior was changed (between Spring versions) to write null fields instead. Which only occurred on those services that relied on null fields being omitted. Fix was easy but finding the bug was difficult.

kubanczyk 4y ago

Microservice is a module. A module that got separated by a network layer, most often due to somebody's momentary lapse of judgement. It's encouraging that you forbid the next person to fall into identical trap (you effectively say: this kind of remote module must not use further remote modules). Alas... they can, and they will.