From 972d42d925e6cae3f8eebd9b21d445e06c2eb386 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sun, 15 Mar 2020 15:50:36 -0400 Subject: content: rename articles to reinforce convention of short URLs The Go blog started out on Blogger (http://web.archive.org/web/20100325005843/http://blog.golang.org/). Later, we moved to the current self-hosted blog server with extra Go-specific functionality like playground snippets. The old Blogger posts have very long URLs that Blogger chose for us, such as "go-programming-language-turns-two" or "two-go-talks-lexical-scanning-in-go-and", predating the convention of giving posts shorter, more share-friendly, typeable names. The conversion of the old Blogger posts also predated the convention of putting supporting files in a subdirectory. The result is that although we've established new conventions, you wouldn't know by listing the directory - the old Blogger content presents a conflicting picture. This commit renames the posts with very long names to have shorter, more share-friendly names, and it moves all supporting files to subdirectories. It also adds a README documenting the conventions. For example, blog.golang.org/go-programming-language-turns-two is now blog.golang.org/2years, matching our more recent birthday post URLs, and its supporting files are moved to the new 2years/ directory. The old URLs redirect to the new ones. Change-Id: I9f46a790c2c8fab8459aeda73d4e3d2efc86d88f Reviewed-on: https://go-review.googlesource.com/c/blog/+/223599 Run-TryBot: Russ Cox Reviewed-by: Andrew Bonventre --- content/appengine-scalable.article | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 content/appengine-scalable.article (limited to 'content/appengine-scalable.article') diff --git a/content/appengine-scalable.article b/content/appengine-scalable.article new file mode 100644 index 0000000..4a91040 --- /dev/null +++ b/content/appengine-scalable.article @@ -0,0 +1,35 @@ +# Writing scalable App Engine applications +1 Nov 2011 +Tags: appengine, optimization +Summary: How to build scalable web applications using Go with Google App Engine. +OldURL: /writing-scalable-app-engine + +David Symonds + +## + +Back in May, we [announced](https://blog.golang.org/2011/05/go-and-google-app-engine.html) +the Go runtime for App Engine. +Since then, we've opened it up for everyone to use, +added many new APIs, and improved performance. +We have been thrilled by all the interesting ways that people are using Go on App Engine. +One of the key benefits of the Go runtime, +apart from working in a fantastic language, +is that it has high performance. +Go applications compile to native code, with no interpreter or virtual machine +getting between your program and the machine. + +Making your web application fast is important because it is well known that +a web site's latency has a measurable impact on user happiness, +and [Google web search uses it as a ranking factor](https://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html). +Also announced in May was that App Engine would be [leaving its Preview status](http://googleappengine.blogspot.com/2011/05/year-ahead-for-google-app-engine.html) +and transitioning to a [new pricing model](https://www.google.com/enterprise/cloud/appengine/pricing.html), +providing another reason to write efficient App Engine applications. + +To make it easier for Go developers using App Engine to write highly efficient, +scalable applications, we recently updated some existing App Engine articles +to include snippets of Go source code and to link to relevant Go documentation. + + - [Best practices for writing scalable applications](http://code.google.com/appengine/articles/scaling/overview.html) + + - [Managing Your App's Resource Usage](http://code.google.com/appengine/articles/managing-resources.html) -- cgit v1.2.3