201–210 of 233 posts
Earlier quoted context omitted.
Maybe direct these questions to a C-level employee at Uber who could potentially answer them for you?
There are no doubt lots of Uber employees that post here. This is an appropriate forum to ask.
Earlier quoted context omitted.
I never claimed that it is always worth it to switch because of egress costs, but that egress costs are a reason to switch. If I ran my sites on AWS it would 100x the cost of running it.
These were your words > Egress price makes it worth migrating away from those three. > Even if the alternate cloud provider goes offline for an entire day it still would be worth it financially compared to AWS because egress is so expensive there. You never qualified either with “in my particular use case”. If you had, I would have had no argument. I haven’t been flown into your company along with SAs, sales, project…
This suggests you are looking for a single example where the pricing of the big 3 is compratively high compared to the competition at a point where it worth it to switch. I gave the example that the price of egress is one cost which is not competitive. If I had instead said that SQS was not competitive obviously that wouldn't matter to businesses that don't use it enough to make a difference.
Earlier quoted context omitted.
Where does a line cook's use case fit in it? From what I know, uber eats sends a order to a restaurant, an employee manually punches in the order on their POS system, and the order ticket goes into the kitchen
You don't think there are a variety of people at a restaurant who might interact with the system? Is this particular detail so very important to the point of the parent comment?
Earlier quoted context omitted.
It's not clear to me that being completely unaware of your infrastructure is a good thing. I don't think it's too much trouble to ask an engineer to understand k8s and think about where their service will live, even if it's a ci system that actually deploys. Furthermore, many layers of abstraction, especially in-house abstraction, just mean you have more code to maintain, another system for people to learn, and exist…
All it takes is for one microservice to start hanging on a GRPC request, server hardware stops doing some fundamental thing correctly, or some weird network quirk that 10x’s latency to half the switch ports in a rack, and you end up with insane, sophisticated cascade failures. Because engineers don’t have to understand infra, it often spans geographies and failure domains in unanticipated, undetectable ways. In my op…
Even in a 100 person startup that I worked for where I designed the infrastructure and the best practices and wrote the initial proof of concept code and best practices for about 15 microservices it got to the point where I couldn’t understand everything and had to hire people to separate out the responsibilities.
We sold access to micro services to large health care organizations for their websites and mobile app's. We aggregated publicly available data on providers like licenses, education etc.
Our scaling stood up as we added clients that could increase demand by 20% overnight and when a little worldwide pandemic happened in 2020 causing our traffic to spike
It seems like they’ve gotten to the “holy grail” of deployment where developers don’t have to worry about infrastructure at all in theory. I’ve seen many teams go for simple/leaky abstractions on top Kubernetes to provide a similar solution, which is tempting because it’s easy and flexible. The problem is then all your devs need to be trained in all the complexities of Kubernetes deployments anyway. Hopefully Uber ab…
None of the layers of abstraction are perfect. You have to deal with the whole mess all the way down. We've had individual EC2 instances go bad where I currently work, with Amazon acknowledging a hardware problem after a ticket is raised. The reality is, quickly resolving the issue means detecting it and moving off of the physical machine. Naturally our tooling has no convenient way to do that, because we have layers…
Earlier quoted context omitted.
So we're going to get to the point where everyone gets their own microsevice, right?
That is unironically a better way to do it than anywhere I've worked that does microservices. My experience with microservice shops is you have one macromonolith with 50 people working on it (which has all the problems of a monolith and none of the benefits), 5 actual decent microservices with a team or individual that properly maintains them, and 100 random utility micro"services" that are like 3 lines of code, used…
Earlier quoted context omitted.
These were your words > Egress price makes it worth migrating away from those three. > Even if the alternate cloud provider goes offline for an entire day it still would be worth it financially compared to AWS because egress is so expensive there. You never qualified either with “in my particular use case”. If you had, I would have had no argument. I haven’t been flown into your company along with SAs, sales, project…
>And when has that happened with respect to either GCP, AWS or Azure at a level that it’s worth migrating? This suggests you are looking for a single example where the pricing of the big 3 is compratively high compared to the competition at a point where it worth it to switch. I gave the example that the price of egress is one cost which is not competitive. If I had instead said that SQS was not competitive obviously…
Microsoft and AWS have versions of the “Cloud Adoption Framework”
https://learn.microsoft.com/en-us/azure/cloud-adoption-frame...
https://aws.amazon.com/cloud-adoption-framework/
And the TOGAF framework has something similar
https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap...
I am saying when considering any “large” implementation there are a lot of considerations outside of infrastructure bills.
I’m not saying that every company should go cloud. But the “lenses” you have to look through are multifaceted
I got so excited about reading for Mesos helping in the multi cloud world, potentially as the hypervisor for running k8s
Earlier quoted context omitted.
There are no doubt lots of Uber employees that post here. This is an appropriate forum to ask.
And why do you think they could answer you with any details without going through comms?