AWS and VMware now are partners but it might be only a matter of time before AWS moves to take its own path.
The old days (and by old days I mean two or three years ago) were so much simpler. For those of us following the major public cloud vendors, it was an easy-enough task to classify the various players:
Amazon Web Services (AWS) was the choice of the greenfield operations. Those that didn’t have any legacy to think about and simply wanted to leverage the most forward-looking public cloud.
Microsoft Azure was for those organizations that were existing “Microsoft shops.” Not yet compelling for greenfield workloads, it was the bridge between the old and the new
Google was for the cool kids – those whose primary focus was mobile applications, developer composability and the various other services that Google offers
All that has changed, however with all three players broadening their approaches to more generally cover the needs of both new and existing organizations
On AWS and VMware, a checkered history
Who can forget VMware CEO Pat Gelsinger's pitch to partners from a few years ago. A combative Gelsinger stated clearly:
"We want to own corporate workload. We all lose if they end up in these commodity public clouds. We want to extend our franchise from the private cloud into the public cloud and uniquely enable our customers with the benefits of both. Own the corporate workload now and forever."
Of course, this was back in the day when VMware still had its own ostensibly public cloud offering, vCloudAir. The company has since realized that taking on the big public cloud is a futile strategy and that it’s best hopes lie in helping its existing customers bridge their existing technology stacks into the public cloud.
This is somewhat ironic since VMware came to dominance as a company by making virtualization broadly available. As such, VMware had an integral part in making life unpalatable for the companies who made the bulk of their revenues by selling physical servers – IBM, HP and Intel among them. Virtualization, by allowing physical servers to be driven to ever-higher levels of efficiency and utilization, meant that less individual physical servers were sold. And now VMware was itself being disrupted by new approaches.
Wednesday 8 November 2017
Sunday 29 October 2017
Big Blue's Former CIO Tried to Join AWS, Ends Up at Energy Company
IBM seems to have managed to prevent its former CIO from joining Amazon Web Services.
Jeff S Smith left IBM in May 2017 after being offered a senior contract at AWS.
This move really pissed IBM off because Smith knew all about Big Blue's plans to reorganize his cloud and set sail for Amazon. Therefore, IBM threw a throwing ball at Smith and tried to enforce his non-compete agreement.
This effort seems to have worked, as World Fuel Systems' energy management company last week proclaimed Smith's arrival as chief executive and director of operations.
According to World Fuel Systems, "Smith's agility experience for sales teams will help improve operational performance to deliver a great experience to our customers and suppliers."
The registry read court documents in the case and suggests that IBM and Smith reached an agreement in September and the Southern District of New York was satisfied with the terms and dismissed the case.
Judicial records do not include the details of the agreement, but reveal the arguments used. Smith's team argues that he was not privy to the secret details of the next IBM cloud, his conversations with the AWS people did not reveal the secret and attempts to use Big Blue their non-competition agreement was punitive and an example for the another 1,700 members bound by those agreements. AWS also made considerable efforts to create a job for Smith that would avoid its non-competition.
IBM stated that Smith knew the company well and, therefore, knew that going to AWS was a no-no.
The fact that the parties have moved, each paying its own costs, suggests that common ground has been found. But it's not central enough to allow Smith to work for AWS before his non-competition expires next year. The World Fuels statement, however, does not suggest that Smith's position is temporary: it seems that Big Blue has brought his man to wherever he wants him to go.®
Jeff S Smith left IBM in May 2017 after being offered a senior contract at AWS.
This move really pissed IBM off because Smith knew all about Big Blue's plans to reorganize his cloud and set sail for Amazon. Therefore, IBM threw a throwing ball at Smith and tried to enforce his non-compete agreement.
This effort seems to have worked, as World Fuel Systems' energy management company last week proclaimed Smith's arrival as chief executive and director of operations.
According to World Fuel Systems, "Smith's agility experience for sales teams will help improve operational performance to deliver a great experience to our customers and suppliers."
The registry read court documents in the case and suggests that IBM and Smith reached an agreement in September and the Southern District of New York was satisfied with the terms and dismissed the case.
Judicial records do not include the details of the agreement, but reveal the arguments used. Smith's team argues that he was not privy to the secret details of the next IBM cloud, his conversations with the AWS people did not reveal the secret and attempts to use Big Blue their non-competition agreement was punitive and an example for the another 1,700 members bound by those agreements. AWS also made considerable efforts to create a job for Smith that would avoid its non-competition.
IBM stated that Smith knew the company well and, therefore, knew that going to AWS was a no-no.
The fact that the parties have moved, each paying its own costs, suggests that common ground has been found. But it's not central enough to allow Smith to work for AWS before his non-competition expires next year. The World Fuels statement, however, does not suggest that Smith's position is temporary: it seems that Big Blue has brought his man to wherever he wants him to go.®
Monday 17 July 2017
AWS Solution Architect Associate Exam Real Questions
Sample Question: 26
What is an isolated database environment running in the cloud (Amazon RDS) called?
A. DB Instance
B. DB Unit
C. DB Server
D. DB Volume
Answer: A
What is an isolated database environment running in the cloud (Amazon RDS) called?
A. DB Instance
B. DB Unit
C. DB Server
D. DB Volume
Answer: A
Wednesday 24 May 2017
Section 1: What is Cloud Computing
I have some private servers on my premises, also I have distributed some of my workload on the public cloud, what is this architecture called?
A. Virtual Private Network
B. Private Cloud
C. Virtual Private Cloud
C. Hybrid Cloud
Answer D.
Explanation: This type of architecture would be a hybrid cloud. Why? Because we are using both, the public cloud, and your on premises servers i.e the private cloud. To make this hybrid architecture easy to use, wouldn’t it be better if your private and public cloud were all on the same network(virtually). This is established by including your public cloud servers in a virtual private cloud, and connecting this virtual cloud with your on premise servers using a VPN(Virtual Private Network).
A. Virtual Private Network
B. Private Cloud
C. Virtual Private Cloud
C. Hybrid Cloud
Answer D.
Explanation: This type of architecture would be a hybrid cloud. Why? Because we are using both, the public cloud, and your on premises servers i.e the private cloud. To make this hybrid architecture easy to use, wouldn’t it be better if your private and public cloud were all on the same network(virtually). This is established by including your public cloud servers in a virtual private cloud, and connecting this virtual cloud with your on premise servers using a VPN(Virtual Private Network).
Tuesday 16 May 2017
Wednesday 22 March 2017
Sunday 19 March 2017
Subscribe to:
Posts (Atom)