![]() ![]() I'm not sure if all of these services are supported for all First Generation languages. Maybe I didn't list all of them, some were in the meantime deprecated, full list with past and ongoing deprecations is here. Images - different image operations like rotation, resizing, flipping etc.App Identity - application id (or project id) discovery.Multitenancy (Namespaces API) - support for multi tenancy in several services.Capabilities - detecting outages and scheduled downtimes for specific services like Datastore, Mail, Memcache etc.Task Queue - asynchronous executions of tasks. ![]() Search - service for indexing and searching text data.Integrated services to which I am and will be reffering through the rest of the article and which are available in First Generation runtime are: For a lot of people GAE tooling offered web app developer's dream, since they didn't have to worry about ops, they could write code, run/debug locally and then with one command deploy. Because of that, some people ignored GAE, some people started using GAE, growing apps but then stuck on hindrances which GAE by it's nature implies like usage of some libraries or language restriction. That means that the code you for wrote for GAE applications could be very GAE specific (use of internal GAE APIs), in other words if you would like to migrate off GAE that would meant major code rewrites (depending on the GAE services used). I wasn't there since beginning but later whenever I read some discussion on internet (typically on Hacker News) number one complaint about GAE was vendor lock-in. Through years other languages and services on GAE as well as other products like Cloud Storage or Cloud SQL were introduced which eventually led to formation of Google Cloud Platform. First supported language was Python and in 2009 Java followed. With GAE introduction, Google shared it's own app development workflow at the time with the rest of the world. It offered SDK which could be used for local development and which mimics behavior as in production. Based on intro post promise of App Engine was simple: " Google App Engine gives you access to the same building blocks that Google uses for its own applications, making it easier to build an application that runs reliably, even under heavy load and with large amounts of data." in other words write code and Google will take care of everything else like it does for it self: scalability, deployment, load balancing, security, as well as other services directly included like Memcache, Taskqueues, NoSQL database. It has been 10 years since Google App Engine was launched. It can be also nice nostalgia reading for long time users. For people who are coming to Google Cloud Platform and are thinking about using Google App Engine this can be confusing, so with this article I wanted to bring maybe bit more clarification. So now there is First and Second generations of Standard and also Flexible. This years second generation of standard runtimes for Google App Engine was released. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |