Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Bücher
Zeitschriften
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
MTZ-Fachkongress

Antriebe und Energiesysteme von morgen


Austausch von Automobil- und Energiewirtschaft

Am 14./15. Mai geht es in Chemnitz um die Mobilitätswende durch Elektro- und Wasserstofffahrzeuge.
Erweiterte Suche
Anmelden
nach oben

2009 | Buch

Google App Engine Kapitel lesen Erstes Kapitel lesen

Developing with Google App Engine

verfasst von: Eugene Ciurana

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten
insite
SUCHEN

Über dieses Buch

Developing with Google App Engine introduces development with Google App Engine, a platform that provides developers and users with infrastructure Google itself uses to develop and deploy massively scalable applications.

Introduction to concepts Development with App Engine Deployment into App Engine

Inhaltsverzeichnis

Frontmatter
Chapter 1. Google App Engine
Abstract
This chapter provides an introduction to Google App Engine concepts. We’ll look at development methodology and how App Engine implements cloud computing concepts by providing both development and runtime services.
Chapter 2. Exploring the SDK
Abstract
An App Engine project consists of several files that handle all aspects of the application. This chapter presents a strong password generation application to introduce the project layout, configuration requirements, the local development web server, debugging techniques, and techniques for publishing the application to the web.
Chapter 3. The Design of a Google App Engine Application
Abstract
Chapters 1 and 2 provided an introduction to the App Engine concepts and tools but didn’t quite deal with application design and implementation. The rest of this book will focus on how to develop complete applications using the API features and how to manage the application once it’s been published.
Chapter 4. Building an Application
Abstract
The previous chapters laid the foundation for starting, writing, and deploying applications for Google App Engine. This chapter is about how to lay out the web pages for the application, how to use webapp and other frameworks, and how to deal with dynamic content, static files, page formatting, and JavaScript in the context of the application.
Chapter 5. What About the Users?
Abstract
Applications must have some way of authenticating users. Authentication is just the process of validating that a user has access to the resources that the application provides. Credentials exchange is the most common authentication mechanism.
Chapter 6. Using the Datastore
Abstract
The Datastore is the main scalability feature for Google App Engine applications. Applications written for App Engine are a set of stateless callbacks. This structure allows for distributing requests across an unlimited number of servers. Scalability would be compromised, however, if the application relied on relational database technology for scaling, since requests from multiple servers would somehow have to be tied to some shared connection pool and some kind of shared caching. That would limit applications to using only a subset of Google’s servers. It would also invalidate the scalability reasons for putting applications on the cloud and wouldn’t be much different from running on a traditional environment.
Chapter 7. Memcache and Session Data
Abstract
The stateless nature of a Google App Engine application necessitates end-user data persistence in some mechanism that will survive multiple calls across multiple servers, since there is no guarantee that two sequential calls to an event handler will execute in the same server. This stateless nature precludes the use of traditional session data mechanisms, since sessions tend to be tied to a specific server. Scalable architectures that use multiple servers for session handling also implement some mechanism for caching and sharing session-specific data. Google App Engine is not an exception.
Chapter 8. Mail, URL Fetching, and Image Manipulation
Abstract
Google App Engine is an evolving platform. It was released as a preview, and Google added new features as this book was being written and will possibly offer even more by the time you read it.
Chapter 9. Managing the Application
Abstract
The Admin Console is the web interface used for managing App Engine applications, and it provides functions for
  • Creating and registering new applications, as described in Chapter 2
  • Managing domains and subdomains
  • Analyzing traffic and data logs
  • Managing the Datastore and indexes
  • Managing version control and deployment
  • Inviting other developers or application administrators to participate in a project
Backmatter
Metadaten
Titel
Developing with Google App Engine
verfasst von
Eugene Ciurana
Copyright-Jahr
2009
Verlag
Apress
Electronic ISBN
978-1-4302-1832-6
Print ISBN
978-1-4302-1831-9
DOI
https://doi.org/10.1007/978-1-4302-1832-6

Premium Partner

    Bildnachweise