Are Amazon's Web Services Going Open Source?
ruphus13 writes "Amazon has been one of the early movers in the cloud computing space, with its AWS offerings, including S3 and EC2. Now, there is a lot of chatter around the imminent open sourcing of all its APIs and services and the impact that will have on the other 'clouds' out there — public or private. From the article, 'Amazon faces significant threats from open source cloud computing efforts if it pursues a purely proprietary path [...] Amazon can't ignore the cost advantages and diversity of product offerings that open source players are already offering in the cloud computing space. The company's best move is to open source its tools, which will end up diversifying them, play on a level field in terms of cost with the open source alternatives, and charge for services. Absent these moves, the company will lose potential customers to free, open source alternatives [...] Word is Amazon's legal team is currently 'investigating' open sourcing their various web services API's including EC2, S3, etc.', although these have not been confirmed by Amazon."
With all the effort Amazon has put behind defending its products like Kindle from open source meddling, I would be shocked if they reversed their business strategy.
http://www.eucalyptus.com/open/
Folks may be familiar with the open source EC2 "clone" (or whatever) Eucalyptus. The latest version even has Elastic Block Storage support. Is anyone using it in anger?
The Army reading list
Doesn't mean that they'll do it.
Up to now, every "cloud" solution has been completely different, meaning that once you invest in getting one to work, you lose much of that investment if try moving to another. There are *lots* of important dimensions to compete on -- bandwidth cost, CPU cost, RAM cost, OS selection, security, privacy, reliability, reliability, and did I mention reliability? -- but until there is a common platform among vendors, it's all apples and oranges comparison.
Open source would change all that.
Suddenly, I can compare the cost of building it myself to the cost of having Amanzon do it. Due to scale, Amazon should win, but maybe I want to pay for less reliability for my development environment, or I want to pay for more reliability by duplicating that environment among several vendors, or I want to keep the super-sensitive data on my own data haven. Win, win, win.
rohypnol-lover writes "Microsoft has been one of the early movers in the operating system space, with its XP offerings, including SP2 and SP3. Now, there is a lot of chatter around the imminent open sourcing of all its APIs and services and the impact that will have on the other 'operating systems' out there -- public or private. From the article, 'Microsoft faces significant threats from open source operating systems if it pursues a purely proprietary path [...] Microsoft can't ignore the cost advantages and diversity of product offerings that open source players are already offering in the operating system space. The company's best move is to open source its OSes, which will end up diversifying them, play on a level field in terms of cost with the open source alternatives, and charge for services. Absent these moves, the company will lose potential customers to free, open source alternatives [...] Word is Microsoft's legal team is currently 'investigating' open sourcing their various OS API's including SP2, SP3, etc.', although these have not been confirmed by Microsoft."
Their whole business model is based on leasing you the marginal computer power they have at their disposal, not at leasing you code or algorithms.
It's not like you can take the code for S3 and instantly offer a cut-rate S3 service, you need to have the throughput and backend storage they have, and processes they use to manage it efficiently. That's what they sell, and really open-sourcing the systems will only make their services more useful and ubiquitous, because people who want to build a simple hash-database or elastic storage or compute cloud for their org will be able to use these off-the-shelf. And then all of the sudden, AWS has another potential client to either 1) sell compute services to, when the organization outgrows its hardware, and 2) possibly buy cycles and storage from, when amazon deems it reasonable to ship other people piece-work to take the load off their infrastructure. They don't have the tech to do (2) yet in a completely secure way, but it's really not that crazy a possibility and it seems like the next logical step.
Don't blame me, I voted for Baltar.
Whenever I see one of these articles, I always think, exactly WHAT are they (thinking about) open sourcing? And what are the terms.
At level zero, it could be that Amazon merely intends to submit their API's and network protocols to a convenient standards body (ECMA would be an outstanding choice; the world loves their Active-X standard). Of course, this would be an instance of (at best) "open standards" rather than "open source", but journalists and bloggers can be lazy and often don't understand the difference.
Next level up, they could open source a smattering of tools and sample applications designed to help developers better understand and work with their APIs. Of course, this is nothing new - proprietary software vendors (including Microsoft) have done this for years, if not decades.
Finally, they could go the Oracle/Sun route (think MySQL and Java, the latter with its new garbage collector). Everything about the software looks like FOSS, and it seems that you could get a free ride if you're willing to get your hands dirty with the source code; but it turns out that if you want to do serious enterprise or commercial work, you need to pay the man for support and/or proprietary developer's licenses. Big time.
An open API (whatever that is) is not the same as an open source program. If they were releasing the code that makes EC2 work, that would really be newsworthy. Of course, it'll never happen. Making their API accessible is just a way to get more people using their service.
GeoCities. No kidding.
If you commoditize your service to that extent, so will everyone else. You're not going to be able to charge any more than your expenses + SFA.
You'll notice IBM are selling software, services and servers to cloud vendors, not particularly trying to get in on the act themselves, despite having a fearsome service division. They're selling the spades and picks in the gold rush.
Deleted
As I understand it, cloud computing is just "vague" deployment; kind of like roaming hosting, in the sense of roaming mobile phone connections. You don't care what computer you're running on, where it is, or even how powerful it is... you just write the software to a specific API, and the cloud computing services guarantee to meet that API, wherever they put your app. If you need more power, you just buy more resources, and your software scales using the fixed API. So you write your webapp (or supercomputing app, or search engine, or MMO server, or whatever), and the underlying OS/hosting/deployment/administration are handled for you.
There is no group of people of any significant size that would pay to use Amazon services only if they were open source.
Indeed they could lose customers to other providers that provide the same software at up to zero cost. This also represents a security issue for Amazon Customers.
The advantage would be to gain free programmers for their services. This is not very useful, as in this case they are leveraging their massive investment in internet services for running their company. The more it is useful for others, the more it is useful for them.
I suspect that this is a hopeful rumor of those that feel threatened by the Amazon solutions, and that there is no likely case that they will open source their tools.
What would be the source code of an API? It's clearly not about the source code of the implementation. And aren't the APIs already open? Being accessible is the whole point of an API, I thought. So say again, what are they considering doing? TFA and its source are quite unclear about that, but it seems to be only about some kind of official approval by Amazon that "yes, you can use our API which is already open, which of course you're already doing".
While it would be nice to have more competition in the space, the fact is that we trust Amazon with our bits now. There are other players we could trust, but none with the sheer power of Amazon. Sure they go down once or twice a year, but hey, who among us can claim that nothing in our entire infrastructures never ever goes down? Why would the submitter think that any other current player can keep their service growing and have the same reasonable uptimes that Amazon does? Here in the real world, we don't mind paying for crap that works. That's what makes economies run.
Newsfollow.com
closing the Kindle makes business sense in the same kind of way opening the service infrastructure might. I work for a company that might more seriously consider using their services if we knew we wouldn't loose our portability. Remember, cloud computing vendors tout themselves as a utility, this would be required before they could truly make that happen. And of course, this is my speculation on a rumor, grain meet salt.
Quack, quack.
Kindle source code files: http://www.amazon.com/gp/help/customer/display.html?ie=UTF8&nodeId=200203720&qid=1243644379&sr=1-1
What the hell is that supposed to mean? The APIs are already available; other people implement them.
You can only "open source" source code.
Amazons best bet will be to go Open Source, it's a proven method that will produce better results. Using a EC2 Cloud Open Sourced will truly be a great move, that is if they make it.
the year of the cloud on the desktop
Sooo Ive ben playign thiss ga,e wahere i tke a shot of whisky ervy time i haer a buzzword onslashdot
They say you would need at least a duo core system to run it.
Privacy is terrorism.