#googleappengine

[rentahousecolombia-blog]

Inteligencia Artificial la forma inteligente de conocer y conquistar mercados... #inteligenciaartificial #google #googleappengine #googleia #rentahousecolombia (en Google Colombia) https://www.instagram.com/p/B0I0WCAAuZ9/?igshid=10huou9ga45e9

[gobuzo]

実質2日でDatastoreをFirestore移行した話 - eaglesakuraの技術ブログ

謝罪 ごめんなさいごめんなさいごめんなさいごめんなさいごめんなさいごめんなさいごめんなさいごめんなさい。 本番環境のFirestoreをONにしてしまったのは僕です。 何が起こったのか アプリから利用されるサーバーをGAE/Goで開発していた GCPプロジェクトは、アプリ側とサーバー側が同一プロジェクトを使用していた Service Account使ったり、そっちのほうが都合が良かったから Datastoreを利用してデータを保存していた サーバーはGoogle App Engine / Go(1.9系)を使用していた データは goon ライブラリを通してDatastoreに保存していた F…

[tikudesai39-blog]

DevOpsTech Solutions is expert in DevOps automation, Software build and release management, IT infrastructure services and cloud consultancy.

[mydevstuff-blog]

#proxy #googleappengine #python

[publicitymobile]

Getcha’ Geek On

Most of our blog posts are about new releases, functionality or general musings on the evolving digital and social ecosystems, but we thought we would break from tradition and give you some updates from ‘behind the scenes’ at Publicity. 

WARNING: May contain technical jargon. Please proceed at your own risk :-).

 Google App Engine (GAE) & JPA

Publicity (with the exception of the app on your phone) is all hosted on GAE using their high replication data store. Although JPA is the preferred approach in most solutions (a framework that significantly reduces the number of classes in your database), Google offers their own database SDK which allows us to have greater control over our data tier

Although GAE has introduced a MySQL database option, we are sticking with the NoSQL option for now because not only is it working well for us, but the MySQL option has a different billing model in GAE which may require some architecture changes

Although we use NoSQL, our database tier is transactional thanks to the powerful SDK provided by Google

Domains

One thing most software companies (especially start ups) do not put much focus on is their domain model. We have spent a lot of time on our domain model to ensure that it reflects our business processes

Data Transport Objects (DTOs) are objects within our code that move data around. Our application uses A LOT of DTOs. The advantage of this is that it provides an easy message queue implementation framework that allows us to do asynchronous processing and improve performance

The return on investment we have had so far is it that it has allowed for greater code reuse. The downside, is that we do have a little bit more code to maintain, but we believe that this is the right strategy moving forwards

Modules

Publicity is split into lots of different modules (over 100). Although this adds to the number of classes we have, it makes the code a lot easier to manage

What’s next?

With an application of Publicity’s complexity, maintaining this and continually refactoring/improving it is a job in itself. In addition we are in the early stages of developing our product and continually adding new features, all which require development of the central application

A big priority from a technical perspective is an admin console to allow us to become a fully self service application

[yostivanich]

Google delivered some news for users of its Cloud Platform stable of services at its I/O event on Wednesday. Its Compute Engine service — which competes with Amazon Web Services — will now be available to all users, not just those willing to shell out $400 for support. But it also announced the addition of the most commonly requested feature for its App Engine platform cloud: support for the PHP programming language. Platform clouds like App Engine are designed to make life easier for developers by building and hosting application environments. App Engine, which launched in 2008, already supports Python, Java and Google’s own programming language Go. The fact that Google is adding PHP support, before newer and ostensibly hipper languages such as Ruby or Node.js, reflects PHP’s ongoing importance. Since PHP’s creation, in 1995, it has become both a blessing and a bane to developers. Lately, perhaps, more of a bane. Last year StackExchange co-founder Jeff Atwood cataloged a number of calls for the death of PHP, calling on developers to help make the alternatives good enough to replace PHP. But while Atwood chose Ruby for his new company Discourse, the language lives on for a number of reasons. One of the biggest reasons PHP sticks around is that so many people know how to use it. It also underpins many popular applications, including WordPress, Drupal and Magento. Another plus: it’s very easy to deploy. Developers — even novices — can quickly get it up and running on almost any web server. Ruby and Python can take a little more work, especially if you’re a newbie. Ironically, the cloud technology that was supposed to help get rid of PHP once and for all is now extending its life. When platform clouds like App Engine and Heroku were first created, in part, to make it easier to deploy and host Python and Ruby applications. But soon companies saw the opportunity to apply the platform model to PHP as well. Startups like Orchestra (later acquired by Engine Yard) and PHPFog (now AppFog) emerged. Zend jumped in with its own PHP platform cloud offering. Now most of the major platform clouds — including App Engine and Heroku — support PHP. It makes sense: even companies and developers who are dumping PHP still have old apps that they need to run, and they want to run all their apps in one place. Now, thanks to Google, it will be that much easier to keep that PHP code kicking around for a few more years.

[truekrui-blog]

Google App Engineのtips集 - スティルハウスの書庫

[pirwuaqw-blog]

Google App EngineがSQLデータベースをサポートへ。エンタープライズ向けサービスを拡充 － Publickey