4 ms·

Microservices usually solve organisational problems not the technical ones. Like here it is probably very painful to deploy to the production.

aledalgrande 3y ago
That Rails app pipeline deploys hundreds of PRs a day to `main` https://shopify.engineering/software-release-culture-shopify https://shopify.engineering/software-release-culture-shopify
craigmcnamara 3y ago
Microservices solve revenue problems at cloud hosting and CI companies.
- pelasaco 3y ago
  And maintenence and onboarding.. I guess to find the right balance is the key. I tend to go with monolith and use microservices to offload heavy dutie tasks or to benefit from other languages and framework when they are a better fit for a specific problem domain
  - antupis 3y ago
    yup, monolith goes very long only to the point where you have hundreds of engineers or some very specific niche technical problem that I would start thinking about microservices.
  - arp242 3y ago
    That doesn't sound like "microservices", but like a monolith with a few services split out where it makes sense. People have been doing that for a million years, long before the web and certainly long before "microservices" was coined. It's just "using common sense" basically.
    - pelasaco 3y ago
      I'm not aware of such nuanced definitions. For me a microservice is a one endpoint service, designed to do one task, with full introspection, and deployed on the "cloud". As fair as I know, I can orchestrate them with monoliths and they still microservices.. or where you draw the line between services and microservices? The size of the service itself or with whom it interacts?
      - arp242 3y ago
        There is no One True Definition™, but I think most people understand "microservices" as "an application where splitting the functionality up in small services is core of the architecture", or something along those lines. "We split off 2 things in to small services because it made sense" is rather different. I mean, I don't really care if you call this 'microservices" I guess, but it is different, right?
mrweasel 3y ago
> Microservices usually solve organisational problems Or create organizational problems. - "Who owns the flip-flop service?" - "That's Bob's team, we fired them last summer!".
- mlrtime 3y ago
  "Who owns /monorepo/shopify/infra/cloud/flip-flop/api/foo_bar.rb"? "That's Bob's team..."
WJW 3y ago
It would be without the tooling, yes. Shopify has a merge queue thingy that you can just shove you MR into and it will eventually get around to deploying it. It even gives you a ping on slack when your changes are about to go live IIRC.
dunno7456 3y ago
Oh, "painful" is to work under the sun. Installing a program in a computer is far away from painful.

aledalgrande 3y ago

That Rails app pipeline deploys hundreds of PRs a day to `main` https://shopify.engineering/software-release-culture-shopify https://shopify.engineering/software-release-culture-shopify

craigmcnamara 3y ago

Microservices solve revenue problems at cloud hosting and CI companies.

pelasaco 3y ago
And maintenence and onboarding.. I guess to find the right balance is the key. I tend to go with monolith and use microservices to offload heavy dutie tasks or to benefit from other languages and framework when they are a better fit for a specific problem domain
- antupis 3y ago
  yup, monolith goes very long only to the point where you have hundreds of engineers or some very specific niche technical problem that I would start thinking about microservices.
- arp242 3y ago
  That doesn't sound like "microservices", but like a monolith with a few services split out where it makes sense. People have been doing that for a million years, long before the web and certainly long before "microservices" was coined. It's just "using common sense" basically.
  - pelasaco 3y ago
    I'm not aware of such nuanced definitions. For me a microservice is a one endpoint service, designed to do one task, with full introspection, and deployed on the "cloud". As fair as I know, I can orchestrate them with monoliths and they still microservices.. or where you draw the line between services and microservices? The size of the service itself or with whom it interacts?
    - arp242 3y ago
      There is no One True Definition™, but I think most people understand "microservices" as "an application where splitting the functionality up in small services is core of the architecture", or something along those lines. "We split off 2 things in to small services because it made sense" is rather different. I mean, I don't really care if you call this 'microservices" I guess, but it is different, right?

mrweasel 3y ago

> Microservices usually solve organisational problems Or create organizational problems. - "Who owns the flip-flop service?" - "That's Bob's team, we fired them last summer!".

mlrtime 3y ago
"Who owns /monorepo/shopify/infra/cloud/flip-flop/api/foo_bar.rb"? "That's Bob's team..."

WJW 3y ago

It would be without the tooling, yes. Shopify has a merge queue thingy that you can just shove you MR into and it will eventually get around to deploying it. It even gives you a ping on slack when your changes are about to go live IIRC.

dunno7456 3y ago

Oh, "painful" is to work under the sun. Installing a program in a computer is far away from painful.