Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
seo Google Developer Podcast Episode 15: Google App Engine 2013
Seo Master present to you:
We had the pleasure to talk to some of the Google App Engine team to discuss the recent launch that Dick uses the tagline as "Your apps, our servers". We get to chat with tech lead on the project Kevin Gibbs, product manager Pete Koomen, and Guido van Rossum. I don't think we need to introduce Guido!
The podcast starts out answering why Google App Engine was created, and why Python was chosen as the first language. We then hear about the work that goes into making a language hardened for the platform itself.
Of all of the APIs that we expose in the App Engine back-end, we feel that the Database API is probably the most foreign for the majority of developers. Many are used to the relational model for datastores, and our datastore is different. Kevin talks about these differences, and the ramifications that come with a schema-less store. We then delve into the practicalities of having libraries such as SQL Alchemy support GQL which is a functional subset of SQL.
What about lock-in? This was one of the big questions that came out of the community when we launched App Engine. You can see how open the team is to other solutions, and how they like seeing work such as AppDrop that shows how you can do this. The choice to make the SDK itself fully open source says a lot.
Guido discussed how the Python runtime is indeed the full language, but how some libraries are not there. He talks about the reasons behind the choices, which are mainly related to security. As time goes on more libraries that developers really need will make it into the system, often with equivalent implementations. Although a traditional file system doesn't make sense in the cloud, we could very well see a virtual file system implemented.
We go on to discuss a lot more, including:
You can download the episode directly, or subscribe to the show (click here for iTunes one-click subscribe).2013, By: Seo Master
We had the pleasure to talk to some of the Google App Engine team to discuss the recent launch that Dick uses the tagline as "Your apps, our servers". We get to chat with tech lead on the project Kevin Gibbs, product manager Pete Koomen, and Guido van Rossum. I don't think we need to introduce Guido!
The podcast starts out answering why Google App Engine was created, and why Python was chosen as the first language. We then hear about the work that goes into making a language hardened for the platform itself.
Of all of the APIs that we expose in the App Engine back-end, we feel that the Database API is probably the most foreign for the majority of developers. Many are used to the relational model for datastores, and our datastore is different. Kevin talks about these differences, and the ramifications that come with a schema-less store. We then delve into the practicalities of having libraries such as SQL Alchemy support GQL which is a functional subset of SQL.
What about lock-in? This was one of the big questions that came out of the community when we launched App Engine. You can see how open the team is to other solutions, and how they like seeing work such as AppDrop that shows how you can do this. The choice to make the SDK itself fully open source says a lot.
Guido discussed how the Python runtime is indeed the full language, but how some libraries are not there. He talks about the reasons behind the choices, which are mainly related to security. As time goes on more libraries that developers really need will make it into the system, often with equivalent implementations. Although a traditional file system doesn't make sense in the cloud, we could very well see a virtual file system implemented.
We go on to discuss a lot more, including:
- What restrictions are there for serving your applications?
- What Web frameworks are available?
- Can you develop Web services as well as Web applications? How about gadget and widget?
- What kind of traffic can be expect with the free accounts?
- Can I run these applications on my domain, and integrate with Google Apps?
You can download the episode directly, or subscribe to the show (click here for iTunes one-click subscribe).2013, By: Seo Master
seo Simperium’s use of Google App Engine for Simplenote 2013
Seo Master present to you:
By Mike Johnston and Fred Cheng, co-founders, Simperium
This post is part of Who's at Google I/O, a series of guest blog posts written by developers who are appearing in the Developer Sandbox at Google I/O.
We originally created Simplenote both as a learning exercise and to address what we thought were shortcomings in the original Notes app for the iPhone (Marker Felt font, no ability to search, etc.) The very first version of Simplenote didn't even have syncing!
We've certainly come a long way since then. The Simplenote backend now synchronizes data across devices, the web, and third-party apps while also handling in-app purchases, sharing, and basic metrics. About a year ago, we were accepted to the Y Combinator startup accelerator with something like 20,000 users. Today, with hundreds of thousands of users, we're currently serving 15 million requests daily and providing access to over 500 gigabytes (!) worth of text notes.
Google App Engine is at the heart of it. We made a decision early on to use App Engine so we wouldn't have to worry about scaling, or deploying more servers, or systems administration of any kind. Being able to instantly deploy new versions of code has allowed us to iterate quickly based on feedback we get from our users, and easily test new features in our web app, like the newly added Markdown support.
We consider our syncing capabilities to be core features of Simplenote. They are, in and of themselves, largely responsible for attracting and retaining many of our users. Our goal is to give other developers access to great syncing, too. The next version of our backend is named after our company, Simperium. As a general-purpose, realtime syncing platform intended for third-party use, Simperium's architecture is much more expansive than the Simplenote backend. Yet App Engine still plays a key role. It powers the Simplenote API that is used by dozens of great third-party apps like Notational Velocity. And it continues to power auxiliary systems, like processing payments with Stripe, while bridging effectively with externally hosted systems, like our solution for storing notes as files in the wonderful Dropbox.
We suspected we might outgrow App Engine, but we haven't. Instead, our use of it has evolved along with our needs. Code we wrote for App Engine a year ago continues to hum along today, providing important functionality even as new systems spring up around it.
In fact, we still come up with entirely new ways to use App Engine as well. Just last week we launched an internal system that uses APIs from Twitter, Amazon Web Services, Assistly, and HipChat to pump important business data into our private chat rooms. This was a breeze to write and deploy using App Engine. Such is the mark of a versatile and trustworthy tool: it's the first thing you reach for in your tool belt.
Come see Simperium in the Developer Sandbox at Google I/O on May 10-11.
Mike Johnston was a senior designer and programmer at Irrational Games where he worked on numerous games and prototypes for PC and Xbox 360. Before that he built security software at Entrust.
Fred Cheng hails from Cantaloupe Systems, a venture-backed startup, where he built their infrastructure for wirelessly tracking tens of thousands of vending machines.
Posted by Scott Knaster, Editor
2013, By: Seo Master
 |
| Mike |
 |
| Fred |
This post is part of Who's at Google I/O, a series of guest blog posts written by developers who are appearing in the Developer Sandbox at Google I/O.
We originally created Simplenote both as a learning exercise and to address what we thought were shortcomings in the original Notes app for the iPhone (Marker Felt font, no ability to search, etc.) The very first version of Simplenote didn't even have syncing!
We've certainly come a long way since then. The Simplenote backend now synchronizes data across devices, the web, and third-party apps while also handling in-app purchases, sharing, and basic metrics. About a year ago, we were accepted to the Y Combinator startup accelerator with something like 20,000 users. Today, with hundreds of thousands of users, we're currently serving 15 million requests daily and providing access to over 500 gigabytes (!) worth of text notes.
Google App Engine is at the heart of it. We made a decision early on to use App Engine so we wouldn't have to worry about scaling, or deploying more servers, or systems administration of any kind. Being able to instantly deploy new versions of code has allowed us to iterate quickly based on feedback we get from our users, and easily test new features in our web app, like the newly added Markdown support.
We consider our syncing capabilities to be core features of Simplenote. They are, in and of themselves, largely responsible for attracting and retaining many of our users. Our goal is to give other developers access to great syncing, too. The next version of our backend is named after our company, Simperium. As a general-purpose, realtime syncing platform intended for third-party use, Simperium's architecture is much more expansive than the Simplenote backend. Yet App Engine still plays a key role. It powers the Simplenote API that is used by dozens of great third-party apps like Notational Velocity. And it continues to power auxiliary systems, like processing payments with Stripe, while bridging effectively with externally hosted systems, like our solution for storing notes as files in the wonderful Dropbox.
We suspected we might outgrow App Engine, but we haven't. Instead, our use of it has evolved along with our needs. Code we wrote for App Engine a year ago continues to hum along today, providing important functionality even as new systems spring up around it.
In fact, we still come up with entirely new ways to use App Engine as well. Just last week we launched an internal system that uses APIs from Twitter, Amazon Web Services, Assistly, and HipChat to pump important business data into our private chat rooms. This was a breeze to write and deploy using App Engine. Such is the mark of a versatile and trustworthy tool: it's the first thing you reach for in your tool belt.
Come see Simperium in the Developer Sandbox at Google I/O on May 10-11.
Mike Johnston was a senior designer and programmer at Irrational Games where he worked on numerous games and prototypes for PC and Xbox 360. Before that he built security software at Entrust.
Fred Cheng hails from Cantaloupe Systems, a venture-backed startup, where he built their infrastructure for wirelessly tracking tens of thousands of vending machines.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Google App Engine Hack-a-thon coming to your coast! 2013
Seo Master present to you:
In May, we'll be holding two Google App Engine Hack-a-thons at Google's offices. The first one will be in New York, May 7th, from 10am - 6pm, and the second one in San Francisco, May 16th, 10am - 10pm. This is a great opportunity to get started on Google App Engine. You can code along with us in building an app from start to finish or you can bring your existing apps and get some help and guidance from Google engineers.
Check out the full details of these events and RSVP for either the New York Hack-a-thon or the San Francisco Hack-a-thon. Or both, if you have the frequent flier miles to spare.2013, By: Seo Master
In May, we'll be holding two Google App Engine Hack-a-thons at Google's offices. The first one will be in New York, May 7th, from 10am - 6pm, and the second one in San Francisco, May 16th, 10am - 10pm. This is a great opportunity to get started on Google App Engine. You can code along with us in building an app from start to finish or you can bring your existing apps and get some help and guidance from Google engineers.
Check out the full details of these events and RSVP for either the New York Hack-a-thon or the San Francisco Hack-a-thon. Or both, if you have the frequent flier miles to spare.2013, By: Seo Master
seo Code Review: Start your App Engine and run the cloud offline with your docs 2013
Seo Master present to you:
The big buzz continues to revolve around our Google App Engine launch. We are seeing a host of applications being developed, and were even pleasantly surprised to see people port the APIs allowing you to run App Engine code elsewhere, such as appdrop.com.
One interesting feature to the App Engine which you may not have noticed, is the integration with Google Apps. Not only can you tie an application to your domain (allowing you to have myapp.mydomain.com instead of myapp.appspot.com) but you can restrict access to the given application to only members of your domain. If I ran a company on Google Apps, this would be a nice addition. I could see the small business apps that I need running there.
Jeff Scudder then released a new version of the Google data Python client library which has support for Google App Engine and the Contacts API. If you want to use this in your Google App Engine application you simply need to set
Google Docs offline, and Gears
I was on the road, speaking about Gears and the Open Web in Europe last week, and it was perfect timing to be mixing with the community as Google App Engine came out and I could talk to that too. We also had a few things to talk about with Gears.
We have been getting lots of questions surrounding our stance with the various standards out there, so Aaron Boodman put down our thoughts on the matter in a piece called Gears and Standards. It talks about how we are working with HTML5, and the direction that you will see Gears going. I think it is incredibly exciting to see people realise how Gears is a lot more than "offline", and is actually an open source way to teach browsers new tricks.
Brad Neuberg talked about just that as well as new features in Gears, and tools to help you get your work done, such as PubTools. He also discussed our first Google Gears for Mobile application, done by the Picasa Team. Now the blokes in London can show off pictures of their kids as they slow poke through the city down in the tube.
The biggest news of all though was the launch of Google Docs offline. If you have ever been in the situation where the internet goes flaky right when you just need that bit of info in document, no more. Now you have the option to save docs locally on your computer, so you can access them no matter where you are.
If you would like a refresher course on how to get started with Gears check out Ben Lisbakken's new screencast.
Fun with Maps
The Geo side of the house continued to output great content, including a series of Geo Developer content:
They were also happy to announce that KML is now a standard, and owned by the Open Geospatial Consortium. We have seen a lot of other sites consume and produce KML, so this is a great step.
Finally, a great new feature was added to Google Maps. You can now check out traffic patterns in the future. If you have a commute the following morning, you can check out an estimate of how stuck you will be based on past experience. Obviously, it can't determine if there will be any crashes or anything like that :)
And there's more...
To finish up, a few other interesting items of the week:
I hope you had a great week. Remember that our big developer event Google I/O is now just a few weeks away! We have a few posts from presenters who will be at the event to give you a little look at the content, but the best part will be having the community together to talk in the open.2013, By: Seo Master
The big buzz continues to revolve around our Google App Engine launch. We are seeing a host of applications being developed, and were even pleasantly surprised to see people port the APIs allowing you to run App Engine code elsewhere, such as appdrop.com.
One interesting feature to the App Engine which you may not have noticed, is the integration with Google Apps. Not only can you tie an application to your domain (allowing you to have myapp.mydomain.com instead of myapp.appspot.com) but you can restrict access to the given application to only members of your domain. If I ran a company on Google Apps, this would be a nice addition. I could see the small business apps that I need running there.
Jeff Scudder then released a new version of the Google data Python client library which has support for Google App Engine and the Contacts API. If you want to use this in your Google App Engine application you simply need to set
gdata.service.http_request_handler = gdata.urlfetch to make sure your requests have a path out!Google Docs offline, and Gears
I was on the road, speaking about Gears and the Open Web in Europe last week, and it was perfect timing to be mixing with the community as Google App Engine came out and I could talk to that too. We also had a few things to talk about with Gears.
We have been getting lots of questions surrounding our stance with the various standards out there, so Aaron Boodman put down our thoughts on the matter in a piece called Gears and Standards. It talks about how we are working with HTML5, and the direction that you will see Gears going. I think it is incredibly exciting to see people realise how Gears is a lot more than "offline", and is actually an open source way to teach browsers new tricks.
Brad Neuberg talked about just that as well as new features in Gears, and tools to help you get your work done, such as PubTools. He also discussed our first Google Gears for Mobile application, done by the Picasa Team. Now the blokes in London can show off pictures of their kids as they slow poke through the city down in the tube.
The biggest news of all though was the launch of Google Docs offline. If you have ever been in the situation where the internet goes flaky right when you just need that bit of info in document, no more. Now you have the option to save docs locally on your computer, so you can access them no matter where you are.
If you would like a refresher course on how to get started with Gears check out Ben Lisbakken's new screencast.
Fun with Maps
The Geo side of the house continued to output great content, including a series of Geo Developer content:
- Quick & Dirty KML Creation: With Mano Marks, Pamela Fox, and Christiaan Adams
A demonstration of creating KML visually in Google Earth & Google Maps, and using Spreadsheet Mapper 2.0 - Creating Custom Maps: With John Coryat
A comparison of various ways of overlaying data in the Maps API and an in-depth explanation of creating tile layers and custom map types - GigaPan In-Depth: With Randy Sargent & Ted Morse
A demo of the GigaPan panorama-browsing website and KML files, plus a technical explanation of PhotoOverlay - Dynamic KML: With Mano Marks & Brian Hamlin
An exploration of using dynamic queries from KML, using the NetworkLink, httpQuery, and viewFormat elements, plus a demo of a PostGIS-generated NetworkLink - Mars, Moon, and Sky Map Types: With Noel Gorelick
A talk introducing the non-Earth Maps API map types, plus cool demos of other types of projections used with planetary imagery - Mapping the Votes: With Michael Geary
A whirlwind tour of what it took to create the Elections 2008 Map/Mapplet/Gadget, including SHPfile conversion, Javascript optimization, centroid calculations, Twitter updates collection, Mapplet API tricks, and more. - Google API Talks - Android, KML, Google Maps, Gadgets
A series of 5-minute talks by various developers and Googlers given before Geary's presentation, including an intro to Gadgets/Mapplets.
They were also happy to announce that KML is now a standard, and owned by the Open Geospatial Consortium. We have seen a lot of other sites consume and produce KML, so this is a great step.
Finally, a great new feature was added to Google Maps. You can now check out traffic patterns in the future. If you have a commute the following morning, you can check out an estimate of how stuck you will be based on past experience. Obviously, it can't determine if there will be any crashes or anything like that :)
And there's more...
To finish up, a few other interesting items of the week:
- Amit Singh on the Google Mac team talked about how you can manipulate keyboard LEDs through software and receive Apple infrared remote control events
- I got to interview Bob Lee about his Twubble app, built using GWT
- Dave Astels talked about flakey tests on the toilet
- Google Code now speaks a lot of languages which apparently caused some students to fix their RSS feed parsers as they didn't grok Unicode
I hope you had a great week. Remember that our big developer event Google I/O is now just a few weeks away! We have a few posts from presenters who will be at the event to give you a little look at the content, but the best part will be having the community together to talk in the open.2013, By: Seo Master
seo Wearing our Developers' Shoes 2013
Seo Master present to you: I set a quarterly goal to write an application in my 20% time that uses publicly available Google APIs. While some would call this scenario testing, I refer to it as "method user experience design" (think method acting). The process can often be painful, but I do it in the hope that it will make me a better designer. It puts me in the shoes of our customers who build products on top of Google's products. I read the same documentation, search the web for the same solutions, write code against the same APIs, and deploy to the same infrastructure. From this exercise come product improvements and empathy. I also enjoy attempting to make something useful, sketching with Python and JavaScript (the charcoal and conte crayon of web development), and proving that 20% time is alive and well.
When it came time to pick last quarter's application, I wanted to work with YouTube's APIs for two reasons: I have a background in video (as a filmmaker and as a software designer) and I wanted to share family videos with my oldest brother, who is hard of hearing and learning disabled. Fast forward a few months later and I had CaptionTube, an application for creating captions for YouTube videos. CaptionTube has launched on TestTube and Hiroto has written a post about it on the YouTube blog.
In addition to the YouTube Data and Player APIs, the application is hosted on Google App Engine and uses the Datastore, Google Accounts, Mail, and URLFetch Python APIs. I used several open source software projects to create it: Django and jQuery, and app-engine-patch. If you are attending Google I/O in May and would like to ask me questions about my experience or discuss your experience using Google's developer's products, please look for me in the developer sandbox or office hour sessions.
2013, By: Seo Master
When it came time to pick last quarter's application, I wanted to work with YouTube's APIs for two reasons: I have a background in video (as a filmmaker and as a software designer) and I wanted to share family videos with my oldest brother, who is hard of hearing and learning disabled. Fast forward a few months later and I had CaptionTube, an application for creating captions for YouTube videos. CaptionTube has launched on TestTube and Hiroto has written a post about it on the YouTube blog.
In addition to the YouTube Data and Player APIs, the application is hosted on Google App Engine and uses the Datastore, Google Accounts, Mail, and URLFetch Python APIs. I used several open source software projects to create it: Django and jQuery, and app-engine-patch. If you are attending Google I/O in May and would like to ask me questions about my experience or discuss your experience using Google's developer's products, please look for me in the developer sandbox or office hour sessions.
2013, By: Seo Master
seo ThoughtWorks' Paul Hammant talks about App Engine for Java 2013
Seo Master present to you: Last week we had a number of exciting announcements and we've received a lot of good feedback so far. We've heard from developers who were excited about cron support, intrigued by the Google Secure Data Connector and pleased with database import. However, most of the excitement has been reserved for the new integrated development environment which was created through the marriage of Google-Web-Toolkit (GWT), Google App Engine for Java and the Google Plugin for Eclipse. Now not only can web app developers write both client and server code using the familiar Java language, they can also share and reuse code between client and server.
I wanted to capture some real world developer feedback, so as part of our Developer Profiles series I sat down with Paul Hammant of ThoughtWorks to discuss his first impressions with the platform. As Paul continues to tinker with the platform you can of course follow him on his blog.
If you have a compelling application that you've written with Google App Engine and GWT I'd like to hear about it.
Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.2013, By: Seo Master
I wanted to capture some real world developer feedback, so as part of our Developer Profiles series I sat down with Paul Hammant of ThoughtWorks to discuss his first impressions with the platform. As Paul continues to tinker with the platform you can of course follow him on his blog.
If you have a compelling application that you've written with Google App Engine and GWT I'd like to hear about it.
Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.2013, By: Seo Master
seo Google App Engine at Campfire One 2013
Seo Master present to you:
We just concluded tonight's Campfire One, where we launched a preview release of Google App Engine, a way for developers to run their web applications on Google's infrastructure. We're still processing the videos from the event, which will be up shortly.
To learn more about Google App Engine, check out the documentation or read the team's announcement on the Google App Engine Blog.2013, By: Seo Master
We just concluded tonight's Campfire One, where we launched a preview release of Google App Engine, a way for developers to run their web applications on Google's infrastructure. We're still processing the videos from the event, which will be up shortly.
To learn more about Google App Engine, check out the documentation or read the team's announcement on the Google App Engine Blog.2013, By: Seo Master
seo Standards-based Persistence For Java™ Apps On Google App Engine 2013
Seo Master present to you: When I sat down to write this post I decided to glance back at my last post on this blog. One sentence in particular jumped out at me: "...I would never again feel compelled to build an [Object-Relational] Mapping framework in Java." Well, friends, never say never. Now that we've unveiled an early look at Java support for Google App Engine, I'm thrilled to announce the availability of a JDO and JPA implementation for the App Engine datastore under the Apache 2 open source license.
The App Engine datastore is an incredible piece of technology. Based on Google's own Bigtable, it's one of the key reasons App Engine enables developers to write web applications that scale without infrastructure headaches. But, it isn't necessarily what most of us are accustomed to using for persistence. Wouldn't it be lovely if we could use an existing programming model on top of the datastore API? And wouldn't it be even lovelier if that existing programming model simplified the process of porting web applications on and off App Engine?
Fortunately for us Java developers we have not one, but two persistence standards at our disposal, JDO and JPA. And, to make adopting these persistence standards easier, we have the DataNucleus project (formerly JPOX), which provides plugins that connect these standards to various types of datasources. Andy Jefferson, founder of the DataNucleus project, was not only enthusiastic about our effort to add an App Engine plugin to his project, he was also incredibly helpful (thanks Andy!). I hope you're as excited about the results as I am: Standards-based persistence for the App Engine datastore!
Since App Engine for Python launched almost a year ago I've admired not just the applications that have been built by the developer community but the infrastructure as well. Even though the DataNucleus App Engine plugin was developed by Googlers, it uses the public App Engine APIs that are available to everyone. It uses no backdoors or special privileges. Rather, it is merely the first instance of what I hope will be a torrent of Java infrastructure developed for App Engine for Java. Feel free to peruse the code at http://code.google.com/p/datanucleus-appengine. If you find a bug, send us a patch. And if you think you can do better, do better! There's absolutely nothing stopping you.
2013, By: Seo Master
The App Engine datastore is an incredible piece of technology. Based on Google's own Bigtable, it's one of the key reasons App Engine enables developers to write web applications that scale without infrastructure headaches. But, it isn't necessarily what most of us are accustomed to using for persistence. Wouldn't it be lovely if we could use an existing programming model on top of the datastore API? And wouldn't it be even lovelier if that existing programming model simplified the process of porting web applications on and off App Engine?
Fortunately for us Java developers we have not one, but two persistence standards at our disposal, JDO and JPA. And, to make adopting these persistence standards easier, we have the DataNucleus project (formerly JPOX), which provides plugins that connect these standards to various types of datasources. Andy Jefferson, founder of the DataNucleus project, was not only enthusiastic about our effort to add an App Engine plugin to his project, he was also incredibly helpful (thanks Andy!). I hope you're as excited about the results as I am: Standards-based persistence for the App Engine datastore!
Since App Engine for Python launched almost a year ago I've admired not just the applications that have been built by the developer community but the infrastructure as well. Even though the DataNucleus App Engine plugin was developed by Googlers, it uses the public App Engine APIs that are available to everyone. It uses no backdoors or special privileges. Rather, it is merely the first instance of what I hope will be a torrent of Java infrastructure developed for App Engine for Java. Feel free to peruse the code at http://code.google.com/p/datanucleus-appengine. If you find a bug, send us a patch. And if you think you can do better, do better! There's absolutely nothing stopping you.
2013, By: Seo Master
seo New features for App Engine announced at Campfire One 2013
Seo Master present to you: I'm excited to announce new, highly requested features for App Engine which we unveiled a few minutes ago at Campfire One.
First, we're giving developers an 'early look' at Java™ language support for App Engine. The team has taken a standards based approach, implementing standard Java APIs on top of App Engine where possible. So instead of using the underlying App Engine datastore API, developers can program against Java Data Objects or Java Persistence API.
Developers will also be able to easily build AJAX web applications end-to-end in Java through integration with a new version of Google Web Toolkit and a Google Plugin for Eclipse to support the development experience.
In addition to the Java features, we've also released cron support , data import support, and secure access to data behind the firewall. To learn more, read the full announcement on the App Engine Blog and watch the videos from Campfire One below: (Note: The video will be live soon)
Still needing a developer fix? If you want to dive deeper into these new features, and how to get more out of App Engine and Google Web Toolkit, we encourage you to come talk to us at Google I/O on May 27-28 in San Francisco CA. We'll be there conducting in-depth App Engine and Google Web Toolkit technical sessions and talking to developers. We'd love to hear your feedback about the features, and just see what you are up to.
*Java™ is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
2013, By: Seo Master
First, we're giving developers an 'early look' at Java™ language support for App Engine. The team has taken a standards based approach, implementing standard Java APIs on top of App Engine where possible. So instead of using the underlying App Engine datastore API, developers can program against Java Data Objects or Java Persistence API.
Developers will also be able to easily build AJAX web applications end-to-end in Java through integration with a new version of Google Web Toolkit and a Google Plugin for Eclipse to support the development experience.
In addition to the Java features, we've also released cron support , data import support, and secure access to data behind the firewall. To learn more, read the full announcement on the App Engine Blog and watch the videos from Campfire One below: (Note: The video will be live soon)
Still needing a developer fix? If you want to dive deeper into these new features, and how to get more out of App Engine and Google Web Toolkit, we encourage you to come talk to us at Google I/O on May 27-28 in San Francisco CA. We'll be there conducting in-depth App Engine and Google Web Toolkit technical sessions and talking to developers. We'd love to hear your feedback about the features, and just see what you are up to.
*Java™ is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
2013, By: Seo Master
seo Google Developer Products Help WhiteHouse.gov Connect With America 2013
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.
2013, By: Seo Master
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.
2013, By: Seo Master
seo Google Narratives Series: BuddyPoke 2013
Seo Master present to you: Continuing with the Google Narratives Series, we'd like to profile Google App Engine and OpenSocial developers, Dave Westwood and Randall Ho of BuddyPoke!
Dave and Randall both have backgrounds in 3D and avatars for the last 11+ years, with work in various web 3D games, facial tracking, facial animation, and mobile avatars. They've worked at five companies together - "Dave does all the technical stuff and I'm the technical artist." Simply put, they complement each other perfectly.
Q: Tell us the story of how BuddyPoke was envisioned.
A: We'd always worked for other companies, and disliked the company politics, etc, and always dreamed of just going and doing our own thing. When we saw the huge success of Slide's slide shows on MySpace, we quit our jobs and started work on a 3D pets widget. Facebook apps and OpenSocial weren't live yet and our first project failed miserably because we completely lacked a distribution model with viral channels. Fast forward a bit, and Nintendo Wii is huge with everyone making miis and talking about avatars. There was Playstation Home and Second Life. Also, the Simpsons Movie was just about to released and allowed for you to "Simsponize" yourself. We thought about the 30+ minutes people were putting into customizing their avatars, without any way of doing any cool interaction with friends. We also thought about the interesting fact that most people who installed these types of console games did it mostly for character personalization or "dress up," rather than to actually play the game. Bottom line, we knew we had to do something about it.
Facebook apps then started to take off, and OpenSocial came out. We closely watched what worked and what didn't on Facebook by looking at usage charts of the top 200 apps. After a lot of trial and error, we applied our 3D backgrounds to some of the ideas and came up with a way of doing the 3D rendering in Flash. That's when we came up with BuddyPoke.
Q: Describe your implementation and why you decided on Google App Engine.
A: During the time that we were focused on researching app usage, we noticed that most apps were struggling with scalability. Their difficulties sounded vaguely familiar with our current implementation and we knew we needed to find a platform that would help us avoid the same issue, especially since we were working on the version for MySpace. The main thing here was timing with the release of Google App Engine and the announcement of OpenSocial. All of a sudden we found ourselves able to quickly roll out our app to the various OpenSocial sites without having to worry about scaling.
Q: Tell us about your overall development experience and any obstacles you have encountered along the way.
A: When Google App Engine first came out, the big learning curve was BigTable. Our data models were horrible. Then, after watching Ryan and Brett's talks at I/O, we redid everything and it's running well now. Our only concern is the organization of our code on AppSpot - everything runs on one AppSpot site. If we knew ahead of time of our success, we would have broken the code up in groups to make updating easier. Also, our main ask is XMPP support so that we can implement chat on App Engine.
One last thing...we're thrilled about the success of BuddyPoke. The barrier to entry is so low from a developer's perspective. We never imagined having 3D characters seen by so many people, without having to even think about the technology behind them or without even having to buy a Wii.
We really enjoy hearing from developers in the community about inspiring stories, so if you have something you'd like to share, visit our online submission form. Better yet, come tell us your story at Google I/O. You can also check out Dave & Randall's cool story on the Ning blog!
Thanks Dave & Randall!
2013, By: Seo Master
Dave and Randall both have backgrounds in 3D and avatars for the last 11+ years, with work in various web 3D games, facial tracking, facial animation, and mobile avatars. They've worked at five companies together - "Dave does all the technical stuff and I'm the technical artist." Simply put, they complement each other perfectly.
A: We'd always worked for other companies, and disliked the company politics, etc, and always dreamed of just going and doing our own thing. When we saw the huge success of Slide's slide shows on MySpace, we quit our jobs and started work on a 3D pets widget. Facebook apps and OpenSocial weren't live yet and our first project failed miserably because we completely lacked a distribution model with viral channels. Fast forward a bit, and Nintendo Wii is huge with everyone making miis and talking about avatars. There was Playstation Home and Second Life. Also, the Simpsons Movie was just about to released and allowed for you to "Simsponize" yourself. We thought about the 30+ minutes people were putting into customizing their avatars, without any way of doing any cool interaction with friends. We also thought about the interesting fact that most people who installed these types of console games did it mostly for character personalization or "dress up," rather than to actually play the game. Bottom line, we knew we had to do something about it.
Facebook apps then started to take off, and OpenSocial came out. We closely watched what worked and what didn't on Facebook by looking at usage charts of the top 200 apps. After a lot of trial and error, we applied our 3D backgrounds to some of the ideas and came up with a way of doing the 3D rendering in Flash. That's when we came up with BuddyPoke.
Q: Describe your implementation and why you decided on Google App Engine.
A: During the time that we were focused on researching app usage, we noticed that most apps were struggling with scalability. Their difficulties sounded vaguely familiar with our current implementation and we knew we needed to find a platform that would help us avoid the same issue, especially since we were working on the version for MySpace. The main thing here was timing with the release of Google App Engine and the announcement of OpenSocial. All of a sudden we found ourselves able to quickly roll out our app to the various OpenSocial sites without having to worry about scaling.
Q: Tell us about your overall development experience and any obstacles you have encountered along the way.
A: When Google App Engine first came out, the big learning curve was BigTable. Our data models were horrible. Then, after watching Ryan and Brett's talks at I/O, we redid everything and it's running well now. Our only concern is the organization of our code on AppSpot - everything runs on one AppSpot site. If we knew ahead of time of our success, we would have broken the code up in groups to make updating easier. Also, our main ask is XMPP support so that we can implement chat on App Engine.
One last thing...we're thrilled about the success of BuddyPoke. The barrier to entry is so low from a developer's perspective. We never imagined having 3D characters seen by so many people, without having to even think about the technology behind them or without even having to buy a Wii.
We really enjoy hearing from developers in the community about inspiring stories, so if you have something you'd like to share, visit our online submission form. Better yet, come tell us your story at Google I/O. You can also check out Dave & Randall's cool story on the Ning blog!
Thanks Dave & Randall!
2013, By: Seo Master
seo Go beyond the free limits on Google App Engine 2013
Seo Master present to you:
We just announced that developers can now grow their applications beyond App Engine's free limits that have been in place since it launched last year.
The pricing for resources beyond those free quotas is:
We just announced that developers can now grow their applications beyond App Engine's free limits that have been in place since it launched last year.
The pricing for resources beyond those free quotas is:
- $0.10 per CPU core hour.
- $0.10 per GB of incoming traffic and $0.12 per GB of outgoing traffic
- $0.15 per GB of data stored by the application per month.
- $0.0001 per email recipient for emails sent by the application
seo App Engine 1.4.2 SDK - API Updates and Additions Edition 2013
Seo Master present to you:
2013, By: Seo Master
Google App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. There are no servers to maintain, and we keep the SDK up to date with regular releases. Today’s SDK release, 1.4.2 focuses on improving and updating a few existing App Engine APIs.
Improved XMPP API to help applications better interact with users. Notifications are sent when users sign in and out and when their status changes, and the application can now set presence details to be returned to the user. Subscription and Presence notifications are enabled as inbound services in the application configuration.
Task Queue performance and Task Queue API improvements. First, we’ve increased the maximum rate at which tasks can be processed to 100 tasks/second. Applications can also specify the maximum number of concurrent requests allowed per queue in their queue’s configuration file. This can help you more easily manage how many resources your task queue is consuming. We’ve also added an API that allows you to programmatically delete tasks, instead of managing this manually from the Admin Console.
As always, there are more minor features and issue fixes such as support for JAX-WS complete with a new article on how to build SOAP enabled App Engine apps, as well as support for Django 1.2, so be sure to read the release notes for Java and Python. We’ve also updated the App Engine Roadmap with a few new projects so take a look. And if you have any feedback, please visit the App Engine Groups.
2013, By: Seo Master
seo App Engine Developers - Best Buy's Giftag 2013
Seo Master present to you:
We're constantly impressed at the wide range of applications developers are building with Google developer products. One great example is Giftag, an online gift registry and social sharing application created by the Best Buy social media team. Giftag was first developed on a different platform and launched at DEMO 08. After learning about Google App Engine, the Giftag development team decided to move Giftag on to App Engine and re-launched the application just in time for Black Friday.
In this video they created, the Giftag team shares their thoughts on why they chose to migrate Giftag to App Engine, the APIs they used, what they would like to see from App Engine, and tips on how to get started with App Engine. "Because of the technology of Google App Engine, it's superb about allowing you to scale something that's really popular and not having any cost of doing that." - Curtis Thompson, Giftag Lead Developer
To learn more about Google App Engine, check out our documentation, subscribe to our blog and join our growing community.2013, By: Seo Master
We're constantly impressed at the wide range of applications developers are building with Google developer products. One great example is Giftag, an online gift registry and social sharing application created by the Best Buy social media team. Giftag was first developed on a different platform and launched at DEMO 08. After learning about Google App Engine, the Giftag development team decided to move Giftag on to App Engine and re-launched the application just in time for Black Friday.
In this video they created, the Giftag team shares their thoughts on why they chose to migrate Giftag to App Engine, the APIs they used, what they would like to see from App Engine, and tips on how to get started with App Engine. "Because of the technology of Google App Engine, it's superb about allowing you to scale something that's really popular and not having any cost of doing that." - Curtis Thompson, Giftag Lead Developer
To learn more about Google App Engine, check out our documentation, subscribe to our blog and join our growing community.2013, By: Seo Master