After all AppEngine ja night # 1 by GCPUG @ Nikkei Conference Room
Did you go to a GAE event? My friends love memos! (I don't call it Tokui)
For those who only know the name of GAE Personally, I will list the good points of Google App Engine, the strongest PaaS platform ↑ It may be better to read around first ʕ • ̀ω • ́ʔ✧
Greetings from Mr. Kazunori (@ kazunori279) Google App Engine now and in the past ~ GAE's prosperity, decline and revival ~ @soundTricker Practice of multi-tenant web application using Namespace API @tenntenn The strongest PaaS environment Google App Engine @yosukesuzuki Beer talk Try using Vision API / Translation API from GAE enakai00 @Tomorier who tried to contribute to the community without permission with GAE The story of making a reversi LINE Bot on GAE / Go @orfeon Is GAE / Go + Cloud SQL in Demand? @Kaneshin I tried GAE in China @hayatoy GAE @mtoyoshi in Scala
appengine ja night #1-#10 review @ kazunori279
The flow of the event so far What if the space-filling curve looks like this?
https://docs.google.com/presentation/d/16t76KP7yWHcChK-8kAXSxnhgNDj86gl-1jLA4XmGF0U/edit @soundTricker
** Autoscale, versioning is the default ** It's hard to do with IaaS! ** Use Google Infrastructure **
| Year | Additional features | Supplement |
|---|---|---|
| 2008 | (Announced at Campfire one) | There were many restrictions at first |
| 2009 | Paid version Memcache, Admin Console, image API, GAE/J, Cron, TaskQueue, XMPP, Blobstore |
This time is the most popular GAE/J slim3 used Scala, Groovy,The appearance of JRuby is about to happen Spring Roo,VMWare → There was neither ... |
| 2010 | Datastore Cursor, AppStats, Namespace | |
| 2011 | GAE/Go, backends, High Reprication Datastore Price revision (generally price increase) |
Price revision CPU time → Instance time I was hit. It was still cheaper than other PaaS ... One cause of decline |
| 2012 | Channel API, ndb, Go 1.0, Threads, GCS, Search API, GCE |
ndbIs a masterpiece of Mr. Guido It was quite developed |
| 2013 | socket, php, cloud endpoint, dedicated memcache, cloud playground |
cloud playgroundIs easy |
| Saikin | Relaxation of restrictions, price revision (generally price reduction), Supports multiple languages within the project |
Price revision Datastore I don't have to worry too much Think only when you're speeding |
It was cheap, it was cusso scaled, and it was the most played
Spin-up Java slow (because Java was the most used) supported language Lock-in File system cannot be used Unusable API gar Price revision from (generally price increase)
But it kept evolving
HRD (High Replication Data store) has no obstacles The limit is gradually relaxed (in the past, up to 1000 Datastores) Documents have also increased
SQL is now available, and big queries are all the rage Various mysterious technologies
GAE Flexible Environment β It's nice to have more freedom, but the back side has changed a lot and it's still stable. It's not GAE anymore (just that)
Popularization of containers "I was sick" Autoscale has become common sense Fully managed Good flow Lock-in What is it delicious (Oh yeah w) Good compatibility with the recently popular Go
(In Standard Edition)
| language | Spin up | Library | Supplement |
|---|---|---|---|
| Python | Fast | Many good | taskletCan be parallelized by using Lots of Google sample code |
| Go | Detonation velocity | Somewhat late | Goruchin! SDK version will follow you for the time being |
| Java | Late | As it is | Don't worry about hiring Easy to receive IDE support slim3 Not recently updated ... |
| PHP | Fast | Less | Shirane(゜ ⊿ ゜) Rumors with Onimon |
Please note that there is a lot of outdated information ndb, HRD, Services (formerly Modules) are not available
The development of GAE alone is slow. Follow GCP as a whole Machine learning API, Stackdriver, Firebase, etc. ** Tokyo Region ** ktkr Nexuto wktk
Easy to develop with Stackdriver system Debugger, Trace, Logging
Datastore is not good for anything (old people tend to do it) It's hard for strangers, and now I have Cloud SQL If you want to use it, ask someone who has knowledge. There is a design, it is deep ** @ sinmetal [seems to write] in the technical book of Technical Book 2 (https://twitter.com/sinmetal/status/837522065179566081) ** Yeah?
(Banner distribution tool that spans multiple services) https://www.slideshare.net/takuyaueda967/namespace-apiweb @tenntenn
(reference) Atte Development Technology: Golang and Google App Engine
The language used by Mercari Atte and Mercari is PHP Interference, no specific processing for each service Also used by non-engineers Easy to get rid of
NamespaceAPI For use from multiple apps Settings for each service do not apply to data and code Supports datastore, memcache, TaskQueue, Search
Just look at the Context! There is no function to get Namespace (!), So I wrapped it.
Switch to Namespace with middleware and save in datastore Use the instance part of the URL as a Namespace (use it to ignore other than numbers)
Unify the administrative Namespace Administrative API requires administrator privileges
datastore namespace and type What to do if memcache namespace is local ...?
Pros No effect on other services Development environment can be created immediately As soon as you create a Namespace Disadvantages API required for configuration migration between Namespaces Troublesome local debugging
** Easy multi-tenant with GAE ** ** Making in-house tools with GAE is a good idea ** Access control is easy to use in G suite
https://speakerdeck.com/yosukesuzuki/appengine-at-nikkei @yosukesuzuki
(reference) Personally, I will list the good points of Google App Engine, the strongest PaaS platform
Nikkei electronic version 500,000 paying members, 300 million monthly
200 requests / sec about 1 million / day ** Usage fee 40-50,000 / month ** Half is out of the internet 6 people if the time difference is large when it comes 3-26 instances
** It's okay to play abandoned ** The big obstacle is about October 2012 in the last 5 years
No blue-green deployment, slow container startup Jenkins, Rundeck, Sentry, New Relic, etc. are required (= people who can use it are also required)
py3 yet? Search Subtle? Do not scale Difficult to get out of CI
~~ I can't say I didn't make a note even though I like my friends ~~
https://github.com/GoogleCloudPlatform/appengine-photoalbum-example enakai00
You can make this kind of thing in less than 200 lines, so by all means
http://www.バ蒲田ニュース.jp/ @tomorier If you inadvertently try to make Kamata a fool on Twitter, you will have to see Kamata's wonderful information by being fooled, which is a terrifying service.
https://docs.google.com/presentation/d/1iJHJsRaSgLDU6d0Dqtcs-FVtKEzLzMlfji4MfLPC6NY/edit#slide=id.p @orfeon
LINE API Link in the image With the free version, you can only do 50 places, but it's enough because you only need to hit the hand
https://github.com/kaneshin/playground/tree/master/gae/go-cloudsql @kaneshin (reference) Go + App Engine + Cloud SQL-based Go language web application development
** Where are you addicted to Cloud SQL 2nd gen! ** **
Specified in the format " project: region: instance " in app.yaml
https://cloud.google.com/appengine/docs/standard/go/cloud-sql/#setting-up
https://www.slideshare.net/HayatoYoshikawa/how-to-make-gae-adapt-the-great-firewall @hayatoy
The idea was not
@mtoyoshi
I'm doing my best now! It looks like a place We are waiting for good news
Even if there are quite a lot of access ** quite cheap ** Moreover, it doesn't need any care **, and it's GAE. (Functionally and community-wise) ** The environment is ready ** Now is the time Expect ** Datastore design articles ** in tech books ~~ Or rather, it's surprising that @sinmetal didn't take the stage ~~
Also ** Pizagochisosa (๑´ڡ`๑) **
If you are interested, please go to the user group! → http://gcpug.jp/join
(GAE general reference) Google App Engine as of mid-2016 Personally, I will list the good points of Google App Engine, the strongest PaaS platform GCP Edge Cache