Group items tagged

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

What is cloud computing? Cloud computing is the access to computers and their functionality via the Internet or a local area network. Users of a cloud request this access from a set of web services that manage a pool of computing resources (i.e., machines, network, storage, operating systems, application development environments, application programs). When granted, a fraction of the resources in the pool is dedicated to the requesting user until he or she releases them. It is called "cloud computing" because the user cannot actually see or specify the physical location and organization of the equipment hosting the resources they are ultimately allowed to use. That is, the resources are drawn from a "cloud" of resources when they are granted to a user and returned to the cloud when they are released. A "cloud" is a set of machines and web services that implement cloud computing.

What about privacy in an era of cloud computing? If I store my data in a cloud, is the data in a "closed container" and therefore private under the 4th Amendment? Or is putting data in a cloud analogous to giving the numbers I dial on my phone to the phone company?

"This post is my attempt to disentangle and examine the topic of "Internet platform" in detail. I will go at it by identifying three distinct approaches to providing an Internet platform, and project forward on where I think each of the three approaches will go. At best, I might be able to help make a new landscape clear. At worst, hopefully I can at least provide one framework for future discussion."

Cloud computing is a term used to describe a variety of computing models that involve a collection of computers housed in a secure facility accessed through a network connection, typically the Internet. However, cloud computing isn't new, in fact it has been around since the early 1950s.

Wow-Wow-Wow-Wow-Wow

Towards the end-goal of a thorough comprehension of the field of cloud computing, and a more rapid adoption from the scientific community, we propose in this paper an ontology of this area which demonstrates a dissection of the cloud into five main layers, and illustrates their interrelations as well as their inter-dependency on preceding technologies. The contribution of this paper lies in being one of the first attempts to establish a detailed ontology of the cloud.

Yahoo! and Cloudera have worked together to produce a couple of training videos for Pig. There is Introduction to Pig, a 50 minute talk on Pig, including copious examples of writing Pig Latin scripts, an overview of how Pig works, and a discussion of the advantages of Pig versus other Hadoop interfaces

Pig Training Available Online Yahoo! and Cloudera have worked together to produce a couple of training videos for Pig. There is Introduction to Pig, a 50 minute talk on Pig, including copious examples of writing Pig Latin scripts, an overview of how Pig works, and a discussion of the advantages of Pig versus other Hadoop interfaces

Cloud computing is more than just the latest in a series of attempts to pare down government spending - it's a gateway to unprecedented innovation in a sector known more for bureaucratic inertia.

Cloud computing -- defined by the ACM Computer Communication Review as a large pool of easily usable and accessible virtualized resources that can be dynamically reconfigured to adjust to a variable load and operated on a pay-per-use model -- has been generating considerable attention throughout the high-performance computing community, in both the commercial and academic sectors. This new model is seen as a possible way for researchers to move from processing and managing their own data sets locally, to relying on large, off-site, commercially-managed data clusters.

Cloud services are being talked up as a fundamental shift in web architecture that promises to move us from interconnected silos to a collaborative network of services whose sum is greater than its parts. The problem is that the protocols powering current cloud services; SOAP and a few other assorted HTTP-based protocols are all one way information exchanges. Therefore cloud services aren't real-time, won't scale, and often can't clear the firewall. So, it's time we blow up those barriers and come to Jesus about the protocol that will fuel the SaaS models of tomorrow--that solution is XMPP (also called Jabber) .

hmmm, material snagged from the white paper I worked on.  :O I'm not too surprised, and it is on MS's blog, who technically owns the material anyway.  Great reuse!!

The physical and informational barriers we once used to differentiate between our "private" and "public" selves are being eroded by technology, and the erosion is accelerating. If we persist in utilizing a zero-sum, spatial conception of privacy to implement the Fourth Amendment, we will render it ineffective as a guarantor of privacy in the face of arbitrary government action. If we continue along this path, the Fourth Amendment will become, in effect, an artifact - a device that protects against a limited class of real-world intrusions (which will become increasingly unnecessary given the other alternatives).

The continuously evolving economy has created the need for businesses to have a global presence. Try using the Conferencing services to create a virtual corporate office capable of reaching its employees, clients, and prospective customers in a very efficient and cost-effective manner. You can choose from Operator assisted, reservationless and web conferencing services. At ConnectHere we partner with top T1 provider like Intercall and PGI services and our team of experts provide you with a custom made conferencing solution that is of high quality, is scalable and flexible.

British software developer Sage Group Plc has posted a sharp rise in takeup for its "cloud" computing products and raised hopes of a further cash return to shareholders, sending its shares to a 12-year high.