What Web2.0 means to Cloud?

I discussed the subject with one of colleagues who is a Cloud Computing architect. I’m logging what my comment here

=-=-

To continue our previous talk is a huge discussion. I’d recommend you could start to get involved in http://twitter.com and follow

http://twitter.com/mashable
http://twitter.com/j3ffyang -> me
http://twitter.com/OpenIBM -> I own this too as of being admin for IBM Open Source Global community

When you hit any of above, you can see the bytes come from http://aws.amazon.com actually, which is an IaaS with no doubt. Twitter is a kind of social collaboration network -> an application running over Amazon Web Services (AWS). Twitter doesn’t own any hardware resources. Whenever Twitter needs computing capability, it goes to AWS and AWS fulfills its request… on demand. Even though Twitter sometimes out of service due to its overload.

@ IaaS, AWS not only gives power of hardware (CPU, memory, disk and network…), but also provides plugin / API to connect Twitter with Hadoop… and Simple Queue Service (SQS), and Simple Database (SDB).

You shouldn’t be surprised @ Twitter’s power to gather thousand of thousand developers around it, if keeping our eyes open. (Some reasons of the motivation of social collaboration in term of Web2.0). See these:

http://tweetwheel.com
http://ftags.com
http://tweetvalue.com/
http://www.tweetizen.com/
http://twittersnooze.com/
http://mrtweet.net/home/j3ffyang
http://tweettrail.com/search/hadoop

This list is almost endless. They’re all independent of twitter.com. The above are all SaaS, plugable into Twitter.com where provides API -> http://apiwiki.twitter.com/ and http://twitter.com/downloads – @ PaaS

This is an ecosystem.

  • Share/Bookmark

Comments off

Amazon Java Toolkit for Eclipse

Amazon 2 days ago announced to support Eclipse @ EC2 (Elastic Compute Cloud). Amazon names this service as Amazon Java Toolkit for Eclipse. See this >

http://media.amazonwebservices.com/hdr_toolkit_eclipse.jpg
http://aws.amazon.com/eclipse/

This enriches Amazon’s Platform as a Service (PaaS). The obvious implication behind reads:

  • Include Java API within Amazon’s PaaS
  • Provide elastic computing resource for Java application via Java API / IDE on IaaS
  • Ease the access of Java @ API / plugin on Tool-as-a-Service (TaaS)
  • Widen support to Tomcat container

More info:
Pricing > http://aws.amazon.com/eclipse/#2 , which is Free!
Installation > http://aws.amazon.com/eclipse/#4

  • Share/Bookmark

Comments off

AWS Case Study – MedCommons

Source: http://aws.amazon.com/solutions/case-studies/medcommons/

MedCommons, a health records services provider, gives consumers direct access to their medical information (via web browser or Web service APIs) and allows an easy way to share this information with healthcare providers. These services are evidence of a major healthcare trend in which consumers are taking control of their health and assuming ownership of their healthcare records.
MedCommons

One of MedCommon’s offerings, HealthURL is a personal account hosted on Amazon Web Services. MedCommons HealthURL provides a web-based storage repository for consumers to store and share access to their health records. These temporary or long-term accounts live on Amazon S3 where they meet HIPAA requirements of security and redundancy.

“We choose AWS because of their reputation and the scalability of their solution,” states Adrian Gropper MD, Co-founder and Chief Science Officer. “We use Amazon S3, EC2, Elastic IP to store and host individual HealthURL accounts. Compared to traditional hosting providers, Amazon EC2 was easy to set up and pretty inexpensive. The fact that there’s no bandwidth costs between our gateways and long term storage servers will be a huge cost savings.”

With HealthURL, consumers can open an account and upload PDF files, DICOM imaging, CCR information, and other relevant medical data. Then, using credentials, patients can share access with family members, physicians, specialty providers, large hospital networks, or even employers. The patient maintains control of their identity and privacy by granting or revoking access to others as needed.

HealthURL accounts are a $2/month subscription plus a hosting fee. To determine the hosting fee and charge the subscription cost, MedCommons utilized Amazon DevPay to charge and meter customer usage. “DevPay tracks the actual storage and communications expenses for very large diagnostic imaging objects as well as service fees to be paid by the patient/consumer. This billing system saves a great deal of work and enables our transactional business model to compete with the ad-supported model of Google and Microsoft.”

MedCommons also utilizes Amazon FPS to manage direct and third party billing transactions between consumers and MedCommons or patients and doctors. Both Amazon FPS and DevPay allow MedCommons’ customers to simply pay using the existing payment information stored in their Amazon.com account.

With a scalable solution in place, MedCommons also had to consider HIPAA compliance of their application. “Our app was designed to be hosted in the cloud and patient-centric from the ground up. In order to be HIPAA compliant, we had to design our application to allow careful identity management, detailed activity logs, a secure console system that facilitates audit of users and accounts, a clear access consent mechanism, and a locked down app deployment procedure that provides a minimum attack surface—encryption and SSL certificates.”

“We have saved many man-years of work by going with AWS for our in-the-cloud, on-demand healthcare information service. The capability of usage-based pricing at the patient level adds commerce capabilities not available anywhere else. The confidence in the Amazon brand by consumers everywhere makes it our best choice for in-cloud storage and computing,” says MedCommons’ CEO Bill Donner.

  • Share/Bookmark

Comments off

Does Amazon S3 really save money?

Source: http://news.ycombinator.com/item?id=422225

With a price tag of $0.150/GB/month, storing 1TB of data costs around $150/month on Amazon S3. But this is a recurring amount. So, for the same amount of data it would cost $1800/year and $3600/2-years. And this doesn’t even include the data transfer costs.

Consider the alternative, with colocation the hardware cost of storing 1TB of data on two machines (for redundancy) would be around $1500/year. But this is fixed. And increasing the storage capacity on each machine can be done at the price of $0.1/GB. Which means that a RAID-1+redundant copies of data on multiple servers for 4TB of data could be achieved at $3000/year and $6000/2-years in a colocation facility. Whereas on S3 the same would cost $7200/year and $14,400/2-years.

Also, adding bandwidth+power+h/w replacement costs at a colocation facility would still keep the costs significantly lower than Amazon S3.

Given this math, what is the rationale behind going with Amazon S3? The Smugmug case study of 600TB of data stored on S3 seems misleading.

I do see several services that offer unlimited storage which is actually hosted on S3. For example, Smugmug, Carbonite etc. all offer unlimited storage for a fixed annual fee. Wouldn’t this send the costs out of the roof on Amazon S3?

If your startup is using Amazon S3 for its storage needs, for the benefit of the startup community, can you please elaborate your rationale for choosing this service?

  • Share/Bookmark

Comments off

Opening the Cloud

Open-source cloud-computing tools could give companies greater flexibility.
By Erica Naone

Cloud-computing platforms such as Amazon’s Elastic Compute Cloud (EC2), Microsoft’s Azure Services Platform, and Google App Engine have given many businesses flexible access to computing resources, ushering in an era in which, among other things, startups can operate with much lower infrastructure costs. Instead of having to buy or rent hardware, users can pay for only the processing power that they actually use and are free to use more or less as their needs change.

However, relying on cloud computing comes with drawbacks, including privacy, security, and reliability concerns. So there is now growing interest in open-source cloud-computing tools, for which the source code is freely available. These tools could let companies build and customize their own computing clouds to work alongside more powerful commercial solutions.

One open-source software-infrastructure project, called Eucalyptus, imitates the experience of using EC2 but lets users run programs on their own resources and provides a detailed view of what would otherwise be the black box of cloud-computing services.

Another open-source cloud-computing project is the University of Chicago’s Globus Nimbus, which is widely recognized as having pioneered the field. And a European cloud-computing initiative coordinated by IBM, called RESERVOIR, features several open-source components, including OpenNebula, a tool for managing the virtual machines within a cloud. Even some companies, such as Enomaly and 10gen, are developing open-source cloud-computing tools.

Rich Wolski, a professor in the computer-science department at the University of California, Santa Barbara, who directs the Eucalyptus project, says that his focus is on developing a platform that is easy to use, maintain, and modify. “We actually started from first principles to build something that looks like a cloud,” he says. “As a result, we believe that our thing is more malleable. We can modify it, we can see inside it, we can install it and maintain it in a cloud environment in a more natural way.”

Reuven Cohen, founder and chief technologist of Enomaly, explains that an open-source cloud provides useful flexibility for academics and large companies. For example, he says, a company might want to run most of its computing in a commercial cloud such as that provided by Amazon but use the same software to process sensitive data on its own machines, for added security. Alternatively, a user might want to run software on his or her own resources most of the time, but have the option to expand to a commercial service in times of high demand. In both cases, an open-source cloud-computing interface can offer that flexibility, serving as a complement to the commercial service rather than a replacement.

Indeed, Wolski says that Eucalyptus isn’t meant to be an EC2 killer (for one thing, it’s not designed to scale to the same size). However, he believes that the project can make a productive contribution by offering a simple way to customize programs for use in the cloud. Wolski says that it’s easier to assess a program’s performance when it’s possible to see how it operates both at the interface and from within a cloud.

Wolski says that Eucalyptus will also imitate Amazon’s popular Simple Storage Surface, which allows users to access storage space on demand, as well as its Elastic IP addresses, which keeps the address of Web resources the same, even if the physical location changes.

Ignacio Llorente, a professor in the distributed systems architecture group at the Universidad Complutense de Madrid, in Spain, who works on OpenNebula, says that Eucalyptus’s main advantage is that it uses the popular EC2 interface. However, he adds that “the open-source interface is only one part of the solution. Their back-end [the system's internal management of physical resources and virtual machines] is too basic. A complete cloud solution requires other components.” Llorente says that Eucalyptus is just one example of a growing ecosystem of open-source cloud-computing components.

Wolski expects many of Eucalyptus’s users to be academics interested in studying cloud-computing infrastructure. Although he doubts that such a platform would be used as a distributed system for ordinary computer users, he doesn’t discount the possibility. “You can argue it both ways,” he notes. But Wolski says that he thinks some open-source cloud-computing tool will become important in the future. “If it’s not Eucalyptus, I suspect [it will be] something else,” he says. “There will be an open-source thing that everyone gets excited about and runs in their environment.”

Copyright Technology Review 2008.

  • Share/Bookmark

Comments off

Is Amazon Ready For The Enterprise?

Source: http://www.nytimes.com/…is-amazon-ready-for-the-enterprise-26615.html

Author: ALISTAIR CROLL

Copyright: GigaOm
With a flurry of announcements in recent weeks, Amazon has extended its cloud computing lead. The beta label’s gone. It can run Windows applications. By investing in firms like Elastra, it’s tackling enterprise deployment. And there’s a 99.95 percent uptime guarantee.

Much of this is a pre-emptive strike at Microsoft’s upcoming cloud offering. Microsoft has a huge advantage: It owns the stack from OS and virtual machine through to application. Amazon wants to compete on reliability and performance, rather than software suites and licensing. But there are still some things missing before enterprises will really embrace it.

Back in May, most of the people we asked were more likely to trust Amazon than Microsoft with their enterprise applications. But while enterprise customers are using Amazon already, in many cases that use is limited to a department or a short-term project. If Amazon wants to capture entire IT departments, it needs to prove it’s as good or better than in-house infrastructure. And that means delivering responsive, highly available applications, not just an SLA.

To accomplish this, Amazon needs to tackle performance and availability at an architectural level. When companies build their own applications, they rely on building blocks like load-balancing, WAN acceleration, managed DNS and redundant data centers. Fortunately, this is where much of Amazon’s roadmap leads.

  • Network performance: Amazon’s CDN will get static content closer to users. With availability zones, Amazon can also get computation near the edge. All of this reduces the time it takes to deliver bits to users. But it can be faster still: Modern enterprises squeeze every millisecond out of the network. Amazon should also add route optimization, HTTP and TCP optimization to really address network delay.
  • Amazon’s plans for integrated scaling, monitoring, and load balancing in EC2

  • Processing performance: Internet architects improve server performance with load-balancing. First send the request to the fastest data center, then send it to the fastest machine in that data center. If there aren’t any fast machines, the newly announced dynamic scaling will make new ones. All that’s missing (though hinted at) is the ability to measure user experience so EC2 knows when to add new servers. Amazon needs a complete load balancing/monitoring/scaling strategy — with proper controls so IT staff can manage it — to make elastic computing a reality. While they’re at it, a performance SLA would be great, too.
  • Network availability: Those same load balancing technologies improve uptime, using DNS or BGP to bypass unreachable data centers. Amazon needs to launch a SimpleDNS service, tied to availability zones and performance, that gives operators more control. It’s going to have to deal with DNS when it launches its CDN anyway. This looks less like managed DNS (Amazon uses UltraDNS already) and more like products from F5, Citrix or others. Amazon also needs to open up about its carriers and peering arrangements for enterprises to feel comfortable.
  • Processing availability: Big Internet sites don’t achieve high uptime with machines that always work. Instead, they monitor for failure and then have the load balancers take out bad servers. That way, overall availability can be high, even when individual components are broken. Amazon should add load testing and profiling capabilities – particularly since EC2 doesn’t give users deep visibility into the platform — to ensure that applications work worldwide under stress.

As Amazon CTO Werner Vogels pointed out, enterprises like cloud computing for its economics, its elastic capacity and its ability to deliver high reliability. With this roadmap, Amazon goes after Microsoft’s weak spots. But it’s not there yet.

  • Share/Bookmark

Comments off

Gartner: Seven cloud-computing security risks

Source: http://www.infoworld.com/…/Gartner_Seven_cloudcomputing_security_risks_1.html

Cloud computing is fraught with security risks, according to analyst firm Gartner. Smart customers will ask tough questions and consider getting a security assessment from a neutral third party before committing to a cloud vendor, Gartner says in a June report titled “Assessing the Security Risks of Cloud Computing.”

Cloud computing has “unique attributes that require risk assessment in areas such as data integrity, recovery, and privacy, and an evaluation of legal issues in areas such as e-discovery, regulatory compliance, and auditing,” Gartner says. (Compare security products.)

Amazon’s EC2 service and Google’s Google App Engine are examples of cloud computing, which Gartner defines as a type of computing in which “massively scalable IT-enabled capabilities are delivered ‘as a service’ to external customers using Internet technologies.”

[ Learn more about what cloud computing really means and the new breed of utility computing and platform-as-a-service offerings. ]

Customers must demand transparency, avoiding vendors that refuse to provide detailed information on security programs. Ask questions related to the qualifications of policy makers, architects, coders and operators; risk-control processes and technical mechanisms; and the level of testing that’s been done to verify that service and control processes are functioning as intended, and that vendors can identify unanticipated vulnerabilities.

Here are seven of the specific security issues Gartner says customers should raise with vendors before selecting a cloud vendor.

  1. Privileged user access. Sensitive data processed outside the enterprise brings with it an inherent level of risk, because outsourced services bypass the “physical, logical and personnel controls” IT shops exert over in-house programs. Get as much information as you can about the people who manage your data. “Ask providers to supply specific information on the hiring and oversight of privileged administrators, and the controls over their access,” Gartner says.

  2. Regulatory compliance. Customers are ultimately responsible for the security and integrity of their own data, even when it is held by a service provider. Traditional service providers are subjected to external audits and security certifications. Cloud computing providers who refuse to undergo this scrutiny are “signaling that customers can only use them for the most trivial functions,” according to Gartner.

  3. Data location. When you use the cloud, you probably won’t know exactly where your data is hosted. In fact, you might not even know what country it will be stored in. Ask providers if they will commit to storing and processing data in specific jurisdictions, and whether they will make a contractual commitment to obey local privacy requirements on behalf of their customers, Gartner advises.

  4. Data segregation. Data in the cloud is typically in a shared environment alongside data from other customers. Encryption is effective but isn’t a cure-all. “Find out what is done to segregate data at rest,” Gartner advises. The cloud provider should provide evidence that encryption schemes were designed and tested by experienced specialists. “Encryption accidents can make data totally unusable, and even normal encryption can complicate availability,” Gartner says.

  5. Recovery. Even if you don’t know where your data is, a cloud provider should tell you what will happen to your data and service in case of a disaster. “Any offering that does not replicate the data and application infrastructure across multiple sites is vulnerable to a total failure,” Gartner says. Ask your provider if it has “the ability to do a complete restoration, and how long it will take.”

  6. Investigative support. Investigating inappropriate or illegal activity may be impossible in cloud computing, Gartner warns. “Cloud services are especially difficult to investigate, because logging and data for multiple customers may be co-located and may also be spread across an ever-changing set of hosts and data centers. If you cannot get a contractual commitment to support specific forms of investigation, along with evidence that the vendor has already successfully supported such activities, then your only safe assumption is that investigation and discovery requests will be impossible.”

  7. Long-term viability. Ideally, your cloud computing provider will never go broke or get acquired and swallowed up by a larger company. But you must be sure your data will remain available even after such an event. “Ask potential providers how you would get your data back and if it would be in a format that you could import into a replacement application,” Gartner says.

  • Share/Bookmark

Comments off

« Previous entries Next Page » Next Page »