AWS’s Share of Amazon’s Profit
tbray.org
AWS’s Share of Amazon’s Profit
1–10 of 136 posts
Re: AWS’s Share of Amazon’s Profit
#2> So, if this graph is right, then over the last couple of years, somewhere between 50% and 80% of Amazon’s profit has been due to AWS.
Re: AWS’s Share of Amazon’s Profit
#3[deleted]
Re: AWS’s Share of Amazon’s Profit
#4> So, if this graph is right, then over the last couple of years, somewhere between 50% and 80% of Amazon’s profit has been due to AWS.
Which Amazon has thanked almost everyone and their grocery stores for jumping on their bandwagon and spending nearly all their VC money on these services.
Those without any significant revenues will have a hard-time paying up that huge AWS bill if they dared to use K8s or auto-scaling features. I would not want to look at the balance sheet of a companies accounts or quarterly earnings if they cannot generate lots of revenue to pay that AWS bill.
Re: AWS’s Share of Amazon’s Profit
#5> So, if this graph is right, then over the last couple of years, somewhere between 50% and 80% of Amazon’s profit has been due to AWS.
Which Amazon has thanked almost everyone and their grocery stores for jumping on their bandwagon and spending nearly all their VC money on these services. Those without any significant revenues will have a hard-time paying up that huge AWS bill if they dared to use K8s or auto-scaling features. I would not want to look at the balance sheet of a companies accounts or quarterly earnings if they cannot generate lots of…
Under these circumstances, how is AWS lock-in and cost escalation any different from Oracle of the past?
Why would any startup shackle themselves to AWS or any cloud when it's not portable?
Lambdas, in particular, seem like the worst idea in the history of ideas. Once your org adopts them, how do you keep track of these mysterious, business-critical pieces of functionality? How do you ever plan to port them to something else? It seems like you become an Amazon customer forever.
I am incredibly skeptical of cloud at this point. If the other infrastructure and platform concerns of OS upgrades, patches, etc. were handled in an automated way, I'd strongly consider running Kubernetes on bare metal. Data centers and colocation all the way.
I'm eager for self-management of k8s, DBs, Redis, etc. to be automated with tooling. On-prem, but easy to maintain.
edit: wow, from +3 to 0 after an hour. I maintain that I articulated my opinion well in an unbiased way.
Re: AWS’s Share of Amazon’s Profit
#6Earlier quoted context omitted.
Which Amazon has thanked almost everyone and their grocery stores for jumping on their bandwagon and spending nearly all their VC money on these services. Those without any significant revenues will have a hard-time paying up that huge AWS bill if they dared to use K8s or auto-scaling features. I would not want to look at the balance sheet of a companies accounts or quarterly earnings if they cannot generate lots of…
Under these circumstances, how is AWS lock-in and cost escalation any different from Oracle of the past? Why would any startup shackle themselves to AWS or any cloud when it's not portable? Lambdas, in particular, seem like the worst idea in the history of ideas. Once your org adopts them, how do you keep track of these mysterious, business-critical pieces of functionality? How do you ever plan to port them to someth…
> Why would any startup shackle themselves to AWS or any cloud when it's not portable?
Depending on the startup, that may make sense if it allows for fast iteration.
If a startup is trying to achieve product market fit, having a huge AWS bill is a good problem to have, since it means the product is actually successful.
Re: AWS’s Share of Amazon’s Profit
#7Earlier quoted context omitted.
Under these circumstances, how is AWS lock-in and cost escalation any different from Oracle of the past? Why would any startup shackle themselves to AWS or any cloud when it's not portable? Lambdas, in particular, seem like the worst idea in the history of ideas. Once your org adopts them, how do you keep track of these mysterious, business-critical pieces of functionality? How do you ever plan to port them to someth…
> Why would any startup shackle themselves to AWS or any cloud when it's not portable? Depending on the startup, that may make sense if it allows for fast iteration. If a startup is trying to achieve product market fit, having a huge AWS bill is a good problem to have, since it means the product is actually successful.
it’s not even slightly difficult to get a huge AWS bill. people do it on accident because they refuse to put in spend limits.
Re: AWS’s Share of Amazon’s Profit
#8> So, if this graph is right, then over the last couple of years, somewhere between 50% and 80% of Amazon’s profit has been due to AWS.
What makes this even more bonkers to me is this is from something most non-tech people haven’t even heard of.
Re: AWS’s Share of Amazon’s Profit
#9> So, if this graph is right, then over the last couple of years, somewhere between 50% and 80% of Amazon’s profit has been due to AWS.
What makes this even more bonkers to me is this is from something most non-tech people haven’t even heard of.
That makes sense honestly, B2B SaaS is lucrative, steady, and honestly probably moreso than a B2C business could be. Many of the big software players most people have never heard of.
As a consumer, you're almost certainly in a Salesforce system somewhere, but most people have no idea what Salesforce is.
Re: AWS’s Share of Amazon’s Profit
#10Earlier quoted context omitted.
Which Amazon has thanked almost everyone and their grocery stores for jumping on their bandwagon and spending nearly all their VC money on these services. Those without any significant revenues will have a hard-time paying up that huge AWS bill if they dared to use K8s or auto-scaling features. I would not want to look at the balance sheet of a companies accounts or quarterly earnings if they cannot generate lots of…
Under these circumstances, how is AWS lock-in and cost escalation any different from Oracle of the past? Why would any startup shackle themselves to AWS or any cloud when it's not portable? Lambdas, in particular, seem like the worst idea in the history of ideas. Once your org adopts them, how do you keep track of these mysterious, business-critical pieces of functionality? How do you ever plan to port them to someth…
Lambdas, at least the JS ones, are Node.js based and not hard at all to migrate to an alternative cloud service. You can even use a framework that handles all the cloud-specific functionality for you and works across AWS, Azure, GCloud, etc: https://www.serverless.com/
The lock-in really comes from AWS-specific services. Redis, Mongo, etc will have the same API no matter where you're hosting them, so it's pretty trivial to point your client-side code to a different cloud-hosted Redis instance if you find AWS lacking there.