MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you: 2013, By: Seo Master

Seo Master present to you: Last Thursday was a momentous day for citizen participation in government. As you may have heard, President Obama hosted the first online Town Hall meeting with questions submitted and voted on via the internet. The Developer team at Google is honored that two of our technologies, App Engine and Google Web Toolkit, played a role in making this possible.

Google Moderator, built with App Engine and Google Web Toolkit, allows users to submit and vote on questions collaboratively. Originally developed for Google company meetings, it's now available for anyone to use -- but being featured on WhiteHouse.gov offered an unprecedented level of potential traffic and attention. We are thrilled that, thanks to scalable hosting provided by App Engine, Moderator successfully handled traffic from tens of thousands of simultaneous visitors.

During the 48-hour open voting period, the site peaked at 700 hits per second, and 92,934 people submitted 104,073 questions and cast 3,605,984 votes. In total, over one million unique visitors visited the site before the town hall. Even while the site was featured on major news outlets and even the Google homepage the other 50,000 apps built on App Engine were fully supported and experienced no adverse effects.

Since the front-end of Moderator was written using GWT, most user interaction with the site was handled via AJAX requests made from the browser to the server. This enabled a very responsive UI while at the same time keeping bandwidth down. It also made it easy to make some last-minute adjustments to the UI, while ensuring that the JavaScript was compatible with all browsers and all platforms.

As would be expected when a website is utilized by the White House and is featured in the media, there were dramatic, and sometimes unforeseen, upswings in traffic. The graph below shows some of the major surges in load to which App Engine adapted. Conventional web hosting strategies demand the pre-provisioning of enough servers to handle load. Sometimes, as was the case with Moderator on WhiteHouse.gov, accurate traffic estimates can be difficult to develop ahead of time. Fortunately, since Moderator runs on App Engine, all servers and resource allocation were handled automatically. With App Engine, you never need worry whether you've set up enough machines...we'll automatically spin up new servers as traffic grows.


If you haven't tried App Engine yet, we encourage you to join the 150,000 developers who have already built highly scalable web applications on top of Google's computing infrastructure. To learn more, visit code.google.com/appengine/ and make plans to attend our sessions at I/O at the end of May.

By Mike Repass, Product Manager, App Engine2013, By: Seo Master

Seo Master present to you:

Ville

Navneet

By Navneet Joneja, Product Manager,
and Ville Aikas, Technical Lead

When evaluating options for cloud storage, customers often wonder, "How can we optimize our storage to get the highest performance possible?". We believe you shouldn't have to, so we do all the optimization for you – enabling you to focus on your application instead of the minutiae of storage optimization.

The performance of cloud storage services (and indeed most web services) depends on two main factors: the network that moves the data between us and the end user, and the performance of the storage service itself.

1. Network

When you make a request to Google Cloud Storage, one of the key determinants of performance is the network path between you and our servers. This path is critical because if the network is slow or unreliable, it doesn’t really matter how fast the backend is.

There are two main ways to make the network faster:

• Serve the request from as close to the user as possible
• Optimize the network routing between the end-user and the service, including avoiding pockets of network congestion and minimizing the number of network hops between the user and the service.

2. Storage

The other component of system performance is how quickly our servers process your request. The data needs to be managed optimally and once an end-user’s request reaches our servers, we need to serve the request as fast as possible. In a sense, Google Cloud Storage is a gigantic filesystem: authorization checks need to happen, the object in question needs to be looked up, and the data requested needs to be read from the physical storage medium and transferred to the end user, all as efficiently as possible.

So, how do we make sure your requests are served as fast as possible?

• Google Cloud Storage is built on Google’s proprietary network and datacenter technology. We’ve spent more than a decade building out proprietary infrastructure and technology to power Google’s sites (after all, we believe that fast is better than slow). When you use Google Cloud Storage, the same network goes to work for your data.
• We replicate data to multiple data centers and serve an end-user’s request from the nearest data center that holds a copy of the data. We also offer a choice of regions (currently U.S. and Europe) to allow you to keep your data close to where it’s most needed. We then take this one step further. When you upload an object and mark it as cacheable (by setting the standard HTTP Cache-Control header), we automatically figure out how best to serve it using Google’s broad network footprint, including caching it closer to the end-user if possible.
• Finally, you don’t need to worry about optimizing your storage layout (like you would on a physical disk), or the lookups (i.e. directory and naming structure) like you would on most file systems and some other storage services. We take care of all the "file system" optimizations behind the scenes.

In other words, when you store your data on Google Cloud Storage, we do all the background work to make it fast so that you can focus on your application.


Navneet Joneja loves being at the forefront of the next generation of simple and reliable software infrastructure, the foundation on which next-generation technology is being built. When not working, he can usually be found dreaming up new ways to entertain his intensely curious almost-two-year-old.

Ville Aikas likes to work on tools and services that make developers lives easier and "just work". When not busy cranking out code, he loves to play soccer with his kids, build robots and watch F1.

Posted by Scott Knaster, Editor

2013, By: Seo Master