Skip to main content

Home/ Groups/ Cloud Computing
DJHell .

Google App Engine Blog: Early Look at Java language support expanded to 25,000 developers - 0 views

  •  
    Have you signed up to try Google App Engine for Java yet? We were so overwhelmed with the response to our early look at Java support on App Engine that we decided to let more developers in now, without waiting. Thus, we're expanding the early look signups to 25,000 developers, in order to give more of you a chance to try it out. So please sign up, give it a try, and let us know what you think. We've already seen a number of interesting apps built and deployed. Stay tuned for us to point some of the cooler ones out in the coming weeks.
DJHell .

OpenSocial in the Cloud - OpenSocial - 0 views

  • Apps can grow especially fast on social networks, so before you launch your next social app, you should think about how to scale up quickly if your app takes off.
  • Unfortunately, scaling is a complex problem that's hard to solve quickly and expensive to implement.
  • If this app grows to serve millions of users and photos, shared hosting or even a dedicated server won't have the bandwidth or CPU cycles to handle all of the requests. We could invest in more servers and network infrastructure, shard the database, and load-balance requests, but that takes time, money, and expertise. If you'd rather work on the new features of the app, it's time to move into the cloud.
  • ...9 more annotations...
  • It's important to focus on the interactions between the app and your server when designing an application that will run in the cloud. If we standardize the communication protocol and data format, we can easily change the server side implementation without modifying the OpenSocial app.
  • You can configure the makeRequest method to digitally sign the requests your app makes to your server using OAuth's algorithm for parameter signing. This means that when your server receives a request, it can verify that the request came from your application hosted in a specific container. To implement this, the calls to makeRequest in the OpenSocial app spec XML specify that the request should be signed, and the code that handles requests on the server side verifies that a signature is included and valid
  • When our server receives a request, we can verify that it came from our application by checking that the digital signature was signed by a valid container and that the application ID is correct.
  • Since our server isn't storing any relationship data, the app will need to send us a list of user IDs so we can fetch the appropriate photos.
  • Although it's outside the scope of this article, we could provide a mechanism for our OpenSocial app to request a one-time-use token that it would include in the request to upload a photo.
  • Note that the post data is URL-encoded in the request so the post method uses urllib.unquote before splitting the comma-separated list of person IDs.
  • Since the server doesn't store any relationship data, the PhotosHandler class checks the post data of the request for a list of IDs from the container.
  • A common misconception when coding in the cloud is that storage space, CPU cycles, and bandwidth are unlimited. While the cloud hosting provider can, in theory, provide all the resources your app needs, hosting in the cloud ain't free so these resources are limited by your budget. Luckily, OpenSocial provides several mechanisms to cache images and data that will reduce the load on your server.
  • In addition to reducing traffic to our server, this technique has the added benefit of being fast—requesting data from the Persistence API is much faster than making the round trip to your server.
  •  
    Some OpenSocial apps can be written entirely with client-side JavaScript and HTML, leveraging the container to serve the page and store application data. In this case, the app can scale effortlessly because the only request hitting your server is for the gadget specification which is typically cached by the container anyway. However, there are lots of reasons to consider using your own server: * Allows you to write code in the programing language of your choice. * Puts you in control of how much application data you can store. * Lets you combine data from users on multiple social networks. * Enables interaction with the OpenSocial REST API. Setting up an OpenSocial app that uses a third party server is fairly simple. There are a few gotchas and caveats, but the real issues come up when your app becomes successful - serving millions of users and sending thousands of requests per second. Apps can grow especially fast on social networks, so before you launch your next social app, you should think about how to scale up quickly if your app takes off. Unfortunately, scaling is a complex problem that's hard to solve quickly and expensive to implement. Luckily, there are several companies that provide cloud computing resources-places you can store data or run processes on virtual machines. These computing solutions manage huge infrastructures so you can focus on your applications and let the "cloud" handle all the requests and data at scale. This tutorial focuses on a simple photo-sharing app that uses a third-party server to host photos and associated metadata. If this app is going to host millions of images and support many requests per second, we won't be able to run it on a single dedicated host. We'll break the app down and analyze the interactions between the OpenSocial App and the back end server. Then we'll implement the app in the cloud, first using Google App Engine, then leveraging Amazon's S3 data storage service. Finally, we'll look at s
Rich Hintz

Cloud interoperability: Porting Google App Engine (GAE) applications to IBM middleware - 0 views

  •  
    Porting Google App Engine (GAE) applications to IBM middleware
DJHell .

Cloud computing with Amazon Web Services, Part 5: Dataset processing in the cloud with ... - 0 views

  •  
    Learn basic Amazon SimpleDB (SDB) concepts and explore some of the functions provided by boto, an open source Python library for interacting with SDB. In this "Cloud computing with Amazon Web Services" series, learn about cloud computing using Amazon Web Services. Explore how the services provide a compelling alternative for architecting and building scalable, reliable applications. In this article, learn some of the basic concepts and check out some of the functions provided by boto.
DJHell .

Cloud computing with Amazon Web Services, Part 4: Reliable messaging with SQS - 0 views

  •  
    Learn basic Amazon SimpleDB (SDB) concepts and explore some of the functions provided by boto, an open source Python library for interacting with SDB. In this "Cloud computing with Amazon Web Services" series, learn about cloud computing using Amazon Web Services. Explore how the services provide a compelling alternative for architecting and building scalable, reliable applications. In this article, learn about the reliable and scalable messaging service provided by Amazon Simple Queue Service (SQS).
DJHell .

Cloud computing with Amazon Web Services, Part 3: Servers on demand with EC2 - 0 views

  •  
    Learn basic Amazon SimpleDB (SDB) concepts and explore some of the functions provided by boto, an open source Python library for interacting with SDB. In this "Cloud computing with Amazon Web Services" series, learn about cloud computing using Amazon Web Services. Explore how the services provide a compelling alternative for architecting and building scalable, reliable applications. This article introduces you to the virtual servers provided by Amazon Elastic Compute Cloud (EC2). Learn how EC2 can help you configure your applications' computing requirements on the fly and adjust capacity based on demand.
Rich Hintz

Software as a Service sandbox - 1 views

  •  
    Use the IBM Virtual Loaner Program to help you set up an IBM development environment from a remote location and save valuable development time. Start with our new pre-configured SaaS stack featuring WebSphere Application Server Community Edition and DB2 Express C running on Linux, and use the features and support of the Virtual Loaner Program, including the save and restore capability that allows you to continue testing at a later time.
Rich Hintz

IBM developerWorks : IBM EC2 AMI Frequently Asked Questions (FAQs) - 0 views

  •  
    provides clients with access to development and production instances of IBM DB2, Informix Dynamic Server, WebSphere Portal Server, Lotus Web Content Management, WebSphere sMash and Novell's SUSE Linux operating system software in the Amazon Elastic Compute Cloud (Amazon EC2)
Rich Hintz

InfoQ: Amazon Web Services: Building Blocks for True Internet Applications - 0 views

  •  
    presentation discusses how Amazon's Web Services can help Web developers solve common but vexing problems, including scaling. The Elastic Compute Cloud (EC2) and Simple DB are discussed in detail along with the Simple Queue, Simple Storage, and Flexible Payment Services. Each discussion covers basic concepts, example APIs, and brief introductions of case studies.
Rich Hintz

Cloud Computing Poses E-Discovery, Legal Risks - 0 views

  • Cloud Computing Poses E-Discovery, Legal Risks April 10, 2009By Marty Foltyn ORLANDO, Fla. — Cloud computing was a hot topic at this week's Storage Networking World show, but one attorney sounded a warning note about the rush to the cloud. In a presentation titled "Computing (strike that — Litigation) in the Cloud," Steven Teppler, senior counsel at KamberEdelson in New York, said cloud computing and services are a corporate counsel's nightmare. The 2006 e-discovery amendments to the Federal Rules of Civil Procedure (FRCP) changed the legal and corporate information landscape, putting custody and control at top of mind. "Cloud computing means that data may always be in transit," said Teppler, "never anywhere, always somewhere." And that creates a big challenge for corporate counsel. How can they identify "who, when and where" in the cloud? How can organizations handle document retention? And to add another layer of worry, information targeted for the cloud may also be subject to laws requiring privacy and persistent data integrity, and other requirements that the storage manager may not even be aware of. Teppler spelled out the top cloud computing shortcomings: no native security attributes; inadequate or no security provisioning by providers; the lack of understanding of cloud legal issues (a real problem for not only cloud computing providers, but also corporate counsel and IT consultants); and the failure to recognize potential liability from either legal issues or a lack of security. Teppler told the audience that litigation in the cloud is already here. Users of cloud services will need to insist on service level agreement (SLA) terms with their providers to ensure legal and regulatory compliance, searchability, demonstrable customer care (security), provably persistent data integrity and reliability, and demonstrable storage security and integrity for electronically stored information in the cloud.
Rich Hintz

Cloudera Hadoop & Big Data Blog » Blog Archive » Upcoming Functionality in "F... - 0 views

  • Forrest web-based documentation
  •  
    The Fair Scheduler gives each user a configurable share of the cluster when he/she has running jobs, but assigns these resources to other users when the user is inactive.
Rich Hintz

Questions to Ask When Adding a Cloud Computing Component - 0 views

  • Young said IT managers considering a move to the cloud should ask the following questions, for starters: --How portable is the technology and data across international borders? --Who is backing the service provider? --Is the provider certified, and by whom? --Where does the data originate? --How is the identity management process set up? --Who manages physical security at the provider's facilities? --How is change management handled? --What happens to your partnering model?
« First ‹ Previous 241 - 260 of 355 Next › Last »
Showing 20 items per page