Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS just went multi-cloud

acloudguru.com

Post reply on HN
Print view View original

51–60 of 145 posts

Re: AWS just went multi-cloud

#51

Post by hodgesrm »

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

This looks like Amazon FUD. The revenue from alternate clouds will be tiny compared to running in AWS, so there's not much motivation internally to follow through. Also, to make money on other clouds you have to go deep on the products and offer value adds on top. That's not the Amazon model and anyway would be difficult to implement outside of a small number of products. Ergo, this is not something they are really going to do in a meaningful way.

MS SQL Server is a historical analogy. Microsoft could have run the table in the database market by porting to Linux but took years to overcome internal inertia required to run outside Windows.

Re: AWS just went multi-cloud

#52

Post by totaldude87 »

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

with the ever expanding number of services/industries Amazon is operating at(or planning to get into) , the vendor lock in is becoming the real deal. Ex walmart wont go to aws, just because and it probably never will!

So the loss of AWS is gain for Azure(w.r.t Walmart) and frankly apart from the 365 offerings people are taking azure seriously because Azure or Microsoft doesn't compete with other industries on a broader scale!

On the flip side, Netflix uses AWS even though amazon competes it with Prime (not sure for how long), as amazon knocking the doors of new industries such as Big pharma, either they need to move AWS as a separate company or ease them with these kind of multi cloud measures.

Re: AWS just went multi-cloud

#53

Post by totaldude87 »

gauravphoenix wrote: post #49
martamorena9182 wrote: post #18

Earlier quoted context omitted.

See Jeff Bezos' famous comment: "It is better to cannibalize yourself; than let others cannibalize you" This should answer your question and hint what's to come.

I think it was Steve Jobs https://www.crowdspring.com/blog/if-you-dont-cannibalize-you...

and that is what they did

iPhones cannibalized iPods

iPads put a dent on Macs

Re: AWS just went multi-cloud

#54

Post by shitlord »

rory_isAdonk wrote: post #24
shitlord wrote: post #23

Earlier quoted context omitted.

AWS is huge, so YMMV across teams. Some teams have operational and funding issues, so your experience there may be hellish. You could think of it another way and realize that you have your work cut out for you. I previously worked on an AWS team like this and left because I got tired of the grind. On the other hand, a lot of teams are great places to work. Before I left AWS, I worked on a really good team with intell…

That's great to hear. Often online all you hear are the extremes at both ends. I hear that you're basically put on PIP as soon as you join, any truth to this?

I was never a manager so I don't know the official policies around dev lists and PIPs.

Generally, new hires are given a few months to ramp up and become contributing team members. People are usually placed on the dev list if they don't meet expectations, and placed on a PIP if their performance does not improve. I'm guessing it reflects poorly on managers if they devlist someone shortly after hiring them.

During my time at Amazon, I know only one person who was placed on a PIP and he was kind of a bad engineer. But I have heard stories of managers abusing the dev list to meet org-level dev list quotas.

Re: AWS just went multi-cloud

#55

Post by daxfohl »

julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

With anthos and arc, the iaas market is going to be commodity with near zero margin. The writing is on the wall that services will be the more profitable market in the long run. AWS recognizes this and the multi cloud push is the way to maximize on that.

Re: AWS just went multi-cloud

#56

Post by marcinzm »

finikytou wrote: post #22
qz2 wrote: post #21

Earlier quoted context omitted.

Don’t forget their ElasticSearch version. Now that is a shit show.

what do you mean? they have customers using it in prod

AWS could release a literal turd and someone somewhere would use it in production. Which doesn't mean you should too.

Re: AWS just went multi-cloud

#57

Post by julianozen »

rory_isAdonk wrote: post #12
julianozen wrote: post #7

I wonder if Amazon’s theory here is that by offering multi-cloud support they can put decision makers at ease when choosing cloud vendors by making them feel like they’re not getting locked into AWS - but Amazon also expects most customers to mostly only use AWS out of convenience Disclaimer - I used to work for AWS

Is working at AWS hellish? Or once you get in it's just a normal job? I get its heavily dependent on the team, just wondering from your perspective.

I enjoyed my team and the work hours were reasonable. AWS wasn't the type of product work I wanted to keep pursing, but I learned a lot in my time there.

Amazon team's culture vary widely depending on the teams budget, management style and deadlines. Overall I enjoyed my time at Amazon

Re: AWS just went multi-cloud

#58

Post by julianozen »

rory_isAdonk wrote: post #24
shitlord wrote: post #23

Earlier quoted context omitted.

AWS is huge, so YMMV across teams. Some teams have operational and funding issues, so your experience there may be hellish. You could think of it another way and realize that you have your work cut out for you. I previously worked on an AWS team like this and left because I got tired of the grind. On the other hand, a lot of teams are great places to work. Before I left AWS, I worked on a really good team with intell…

That's great to hear. Often online all you hear are the extremes at both ends. I hear that you're basically put on PIP as soon as you join, any truth to this?

No there isnt. I have only known of one person to get a PIP during my 3 years there, and it took way longer then it should've

Re: AWS just went multi-cloud

#59

Post by finikytou »

sullivanmatt wrote: post #42
biohax2015 wrote: post #39

Earlier quoted context omitted.

> There are... quite a number of reasons you should give pause to the idea of running AWS hosted elastic. Care to share some of these reasons?

I can't go into details, but let me say that someone who would be in the know at AWS, very much off the record, told us not to use their hosted elastic because of how terrible it is. Some issues: scaling it is manual (a "managed service" that requires direct management to scale is not a managed service lol), the elastic versions supported are usually woefully out of date, limited customer adoption means that the prod…

I totally agree but if your requirement is just to have elastic for a standard search use case and don't need any new features it might make sense... out of date doesnt mean its garbage.

I am not against manual scaling anyway at some level you always need to do manual scaling on AWS whatever the product...

Re: AWS just went multi-cloud

#60

Post by julianozen »

gigatexal wrote: post #41
shitlord wrote: post #23

Earlier quoted context omitted.

AWS is huge, so YMMV across teams. Some teams have operational and funding issues, so your experience there may be hellish. You could think of it another way and realize that you have your work cut out for you. I previously worked on an AWS team like this and left because I got tired of the grind. On the other hand, a lot of teams are great places to work. Before I left AWS, I worked on a really good team with intell…

Crazy to think that such a profitable unit like AWS could have teams that are hurting for funding. I guess it’s run like that though.

I think AWS teams are not generally hurting for funding. You see that more in retail parts of amazon
Post reply on HN