10 ms·

On one hand, I agree with you catching in all aspects would be near impossible. However similar to Apple, a more focused approach could be viable and profitabl

On one hand, I agree with you catching in all aspects would be near impossible. However similar to Apple, a more focused approach could be viable and profitable much more quickly. AWS has been around for a long time, but they also have tons and tons of feature bloat, and full of redundant services with different pricing. Should I use an ELB or an ALB? Fargate, ECS, EKS, code deploy? The list of services is overwhelming and confusing to most. A new major player with a cleanly architected design from the start with a clear path to happiness could be successful. Though Meta is full of feature bloat so I don't know if they would be the right choice to execute that vision.

notyourwork 4y ago
Your examples aren’t really that good. An ALB is a type of ELB (load balancer). AWS has multiple types, ALBs run on layer 7 and NLBs run on layer 4 of the network stack. They also have classic which are considered deprecated and NAT Gateways. None of this is redundant. Similarly Fargate is a type of long running task you could start and run on an ECS cluster. Think web service running in a container instead of a traditional group of EC2 virtual machines. Tartare tasks are also a higher level virtualization abstraction compared to using EC2 in your ECS cluster. On the surface they all seem redundant because of the sheer breadth but when you start poking at them for a new solution that same breadth affords massive flexibility.
- codegladiator 4y ago
  I think you are just helping make his point.
  - MontyCarloHall 4y ago
    “A monad is just a monoid in the category of endofunctors, what's the problem?”
  - notyourwork 4y ago
    You can get flexibility or simplicity, pick your poison. Not all solutions have the same needs so the idea that there exists a single, simple out of the box solution for every problem is naive at best.
    - soco 4y ago
      Yes and they were advocating for simplicity as a possible (starting) way for Meta.
      - taylodl 4y ago
        Except the complexity wasn't created for the sake of creating complexity - it exists for a reason. You can go the simple route if you happen to be brand new to virtual infrastructure management. The problem is you're going to quickly outgrow your solution and then what? Besides, if you want simple you can go with Wix, Wordpress, or Digital Ocean.
        substation13 4y ago
        I'm sure that at least some of the complexity in AWS exists because they can't go back and refactor their offerings when so many users depend on it.
deleted 4y ago
[deleted]

notyourwork 4y ago

Your examples aren’t really that good. An ALB is a type of ELB (load balancer). AWS has multiple types, ALBs run on layer 7 and NLBs run on layer 4 of the network stack. They also have classic which are considered deprecated and NAT Gateways. None of this is redundant. Similarly Fargate is a type of long running task you could start and run on an ECS cluster. Think web service running in a container instead of a traditional group of EC2 virtual machines. Tartare tasks are also a higher level virtualization abstraction compared to using EC2 in your ECS cluster. On the surface they all seem redundant because of the sheer breadth but when you start poking at them for a new solution that same breadth affords massive flexibility.

codegladiator 4y ago
I think you are just helping make his point.
- MontyCarloHall 4y ago
  “A monad is just a monoid in the category of endofunctors, what's the problem?”
- notyourwork 4y ago
  You can get flexibility or simplicity, pick your poison. Not all solutions have the same needs so the idea that there exists a single, simple out of the box solution for every problem is naive at best.
  - soco 4y ago
    Yes and they were advocating for simplicity as a possible (starting) way for Meta.
    - taylodl 4y ago
      Except the complexity wasn't created for the sake of creating complexity - it exists for a reason. You can go the simple route if you happen to be brand new to virtual infrastructure management. The problem is you're going to quickly outgrow your solution and then what? Besides, if you want simple you can go with Wix, Wordpress, or Digital Ocean.
      - substation13 4y ago
        I'm sure that at least some of the complexity in AWS exists because they can't go back and refactor their offerings when so many users depend on it.

deleted 4y ago

[deleted]