I am pretty sure Amazon's retail business is going to completely dwarf AWS in the long term, because they are currently willing to break even on it (and possibly lose money) just to outdo the competition.
My experience:
I once tried to corner the market on WoW gems by buying out the undercutters and setting my desired price. My money wasn’t long enough.
I really don’t think anyone’s money is long enough :p
By which definition? It’s trivial to switch to a different website to order from, and Target/Walmart/Bestbuy/etc have significant market share.
2. I’m already paying for Amazon Prime. Why not get full use out of it for shipping?
3. Amazon marketplace has network effects. Third party sellers use it because the buyers are there.
4. I wanted to rent a movie on my Roku TV. Again, Amazon already has my payment information and I’m already signed in to Prime Video.
5. I get 3% discounts on my Amazon card when ordering from Amazon.
I’ve been downvoted to oblivion plenty of times about being against the government interfering in $BigTech whether it be Google, Amazon, or Apple so I’m definitely not proposing they should be broken up because of a “monopoly”.
As it stands now, Amazon is a glorified Alibaba that sided with buyers in disputes.
You can find the same things on Amazon on Alibaba, Newegg, bestbuy, Walmart, iTunes, Google Play, the Amazon sellers own websites, etc. the buyer is in no way required or affected negatively by not interacting with Amazon.
So I’m struggling to see the point of labeling Amazon a monopoly when it doesn’t convey any useful information.
Sears is more or less dead. Walmart is struggling to keep market share with amz. With groceries their only saving grace
If price is their long term plan with retail that is a loosing proposal. Once they dominant they might be able to sqeeze the market for a few years maybe a decade but them something else will topple them
Walmart is responsible for the 7th, 8th and 9th largest fortunes in the world built before modern monetary policy. Further they completely changed retail in America.
Those seem like weird counter examples.
It will in revenues but not in profits.
Right now, Wallmart, Exxon, GM etc. 'dwarf' most tech businesses in terms of revenues and the size of their businesses, but the profits are smaller, so tech companies have a higher valuation.
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.
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.
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.
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.
It's used in combination with Azure Active Directory, so the modality isn't 1:1 with AWS. But Managed Identities[3] is a feature that's rolling out across Azure which simplifies the model a bit, since it negates the need to create service principles in AAD beforehand.
[1] https://docs.microsoft.com/en-us/azure/role-based-access-con...
[2] https://docs.microsoft.com/en-us/azure/role-based-access-con...
[3] https://docs.microsoft.com/en-us/azure/active-directory/mana...
You’re always tied into your infrastructure once you have any type of scale. The pain of migration is huge.
I once worked with a company whose entire workflow was integrated with six or seven vendors through APIs.
Have you ever worked in the healthcare industry? The level of lock-in they have to their EMR/EHR would make you cry.
No, you just had downtime, full stop. Failures are inevitable, regardless of whose datacenter you're using. Failure-tolerant architecture design minimizes (or eliminates, if you're lucky) the downtime caused by failures. I'm not saying that's easy or necessarily appropriate depending on the stage of your company, but foisting responsibility onto AWS is missing the point.
Esp if you are not vc backed and infra costs are already near the same order of magnitude as most of the dev team and are running into scaling issues…
The company I work for used to have most of its revenue come from VC-backed startups. Over time that changed as we courted more well-capitalized enterprises. If our VC-backed-startup customers all went bankrupt tomorrow, it would certainly hurt, but it wouldn't kill us, not by a long shot.
I would expect that to be even more true for a product like AWS, not less.
I'd argue that the existence of cloud providers have only accelerated the growth of the tech industry and has in fact put more money in the pockets of tech workers and VCs than there would have been without the existence of an AWS/Azure/GCP/etc
As a consumer, you're almost certainly in a Salesforce system somewhere, but most people have no idea what Salesforce is.
I think many people have heard of John Deere and Monsanto but what about McGregor? They may not be as big as AWS but even with Ag experience I bet there are bigger similar organizations.
I bet there are big custom harvest operations too. We had a two man operation on the Palouse but I heard stories about huge operations out of Texas that migrated through the midwest following harvest cycles.
Here is a list I found from a quick search, try to guess which country the biggest producers is based in or how many of top 5 you expect to have heard of before opening the link.
https://en.wikipedia.org/wiki/ThyssenKrupp
This just keeps getting more interesting.