6 ms·

In 3 years… “Uber saved cost by migrating their micro service to their own colo.” followed by “Uber simplified operations by migrating their micro service platf

In 3 years… “Uber saved cost by migrating their micro service to their own colo.” followed by “Uber simplified operations by migrating their micro service platform to a monolith”.

EduardoBautista 3y ago
[flagged]
- weakwire 3y ago
  Yes, no one said they did that.
  - EduardoBautista 3y ago
    [flagged]
    - arthurcolle 3y ago
      They were making a joke about a hypothetical post in another three years
    - yardstick 3y ago
      The “in 3 years” was meant as a forward looking statement. The post was being sarcastic that Uber will in 3+ years time claim another victory, based on abandoning the cloud.
      - gremlinunderway 3y ago
        Thanks, I also misunderstood "in 3 years" meant forward-looking (i.e. "3 years from now...") rather than backward-looking ("for over 3 years...")
politelemon 3y ago
In 5 years... "We've discovered a new paradigm for efficiently carving up and distributing computational units for our application. We call it, nanofunctions."
- mirekrusin 3y ago
  Later "Lowering cost and dramatically reducing complexity with nanofunctions running on monoecosystem".
  - baz00 3y ago
    Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.
    - deegles 3y ago
      Ultimately it's promotion-driven development.
      - baz00 3y ago
        Yeah I call it Resume Driven Development.
        loxias 3y ago
        Exactly. "What's Kubernetes FOR?" "To the best I can tell, it's a jobs program for our industry."
        deleted 3y ago
        [deleted]
        baz00 3y ago
corney91 3y ago
Might be a good guess, there's precedent of them changing fundamental techology in a similar timeframe... 2013: "Migrating Uber from MySQL to PostgreSQL"[1] 2016: "Why Uber Engineering Switched from Postgres to MySQL"[2] [1] https://www.yumpu.com/en/document/view/53683323/migrating-uber-from-mysql-to-postgresql https://www.yumpu.com/en/document/view/53683323/migrating-ub... [2] https://www.uber.com/en-GB/blog/postgres-to-mysql-migration/ https://www.uber.com/en-GB/blog/postgres-to-mysql-migration/
- liquidpele 3y ago
  More like “we hired a new principal arch who drove a change they personally liked, and everything was better because it allowed a lot of time to fix tech debt”
matwood 3y ago
I'm not sure why this is an issue with a long running system. Business requirements change, knowledge changes, cost structures change, etc... Unfortunately the world isn't static. I'm not sure about you, but when the facts change I also try to change.
deleted 3y ago
[deleted]

In 3 years… “Uber saved cost by migrating their micro service to their own colo.” followed by “Uber simplified operations by migrating their micro service platform to a monolith”.

EduardoBautista 3y ago

[flagged]

weakwire 3y ago
Yes, no one said they did that.
- EduardoBautista 3y ago
  [flagged]
  - arthurcolle 3y ago
    They were making a joke about a hypothetical post in another three years
  - yardstick 3y ago
    The “in 3 years” was meant as a forward looking statement. The post was being sarcastic that Uber will in 3+ years time claim another victory, based on abandoning the cloud.
    - gremlinunderway 3y ago
      Thanks, I also misunderstood "in 3 years" meant forward-looking (i.e. "3 years from now...") rather than backward-looking ("for over 3 years...")

politelemon 3y ago

In 5 years... "We've discovered a new paradigm for efficiently carving up and distributing computational units for our application. We call it, nanofunctions."

mirekrusin 3y ago
Later "Lowering cost and dramatically reducing complexity with nanofunctions running on monoecosystem".
- baz00 3y ago
  Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.
  - deegles 3y ago
    Ultimately it's promotion-driven development.
    - baz00 3y ago
      Yeah I call it Resume Driven Development.
      - loxias 3y ago
        Exactly. "What's Kubernetes FOR?" "To the best I can tell, it's a jobs program for our industry."
        deleted 3y ago
        [deleted]
        baz00 3y ago

corney91 3y ago

Might be a good guess, there's precedent of them changing fundamental techology in a similar timeframe... 2013: "Migrating Uber from MySQL to PostgreSQL"[1] 2016: "Why Uber Engineering Switched from Postgres to MySQL"[2] [1] https://www.yumpu.com/en/document/view/53683323/migrating-uber-from-mysql-to-postgresql https://www.yumpu.com/en/document/view/53683323/migrating-ub... [2] https://www.uber.com/en-GB/blog/postgres-to-mysql-migration/ https://www.uber.com/en-GB/blog/postgres-to-mysql-migration/

liquidpele 3y ago
More like “we hired a new principal arch who drove a change they personally liked, and everything was better because it allowed a lot of time to fix tech debt”

matwood 3y ago

I'm not sure why this is an issue with a long running system. Business requirements change, knowledge changes, cost structures change, etc... Unfortunately the world isn't static. I'm not sure about you, but when the facts change I also try to change.

deleted 3y ago

[deleted]