<story><title>Moving The New York Times Games Platform to Google App Engine</title><url>https://open.nytimes.com/moving-the-new-york-times-games-platform-to-google-app-engine-e9337f2c9444</url></story><parent_chain><item><author>smn1234</author><text>The way you&amp;#x27;ve delivered this &amp;quot;experience&amp;quot; makes you sound like you either work for Google or were asked to make a sponsored statement - for credits or $.</text></item><item><author>neya</author><text>Hey community, let me share my experience with AppEngine. I work in a small firm, where we&amp;#x27;ve developed a massive Software Application comprising of 12 medium-sized apps. I went with Phoenix 1.3 w&amp;#x2F; the new umbrella architecture.&lt;p&gt;With AppEngine, the beauty is that you can have many custom named microservices under one AppEngine project and each microservices can have many versions. You can even decide how much percentage of traffic should be split between each of these microservices.&lt;p&gt;What&amp;#x27;s awesome is, in addition to the standard runtimes (Ruby, Python, Go, Java, etc.) Google also provides something called custom VMs for AppEngine, meaning you can push docker based setups into your AppEngine service, with basically any stack you want. This alone is a HUGE incentive to move to AppEngine because usually custom stack will require you to maintain the server side of things, but with Docker + AppEngine, zero devops. Their network panel is also very intuitive to add&amp;#x2F;delete rules to keep your app secured.&lt;p&gt;I&amp;#x27;ve been using AppEngine for over 4 years now and every time I tried a competitive offering (such as AWS Beanstalk, for example) I&amp;#x27;ve only been disappointed.&lt;p&gt;AppEngine is great for startups. For example, a lesser known feature within AppEngine is their real-time image processing service API. This allows you to scale&amp;#x2F;crop&amp;#x2F;resize images in real time and the service is offered free of charge (except for storage).&lt;p&gt;Works really well for web applications with basic image manipulation requirements.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;cloud.google.com&amp;#x2F;appengine&amp;#x2F;docs&amp;#x2F;standard&amp;#x2F;python&amp;#x2F;images&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;cloud.google.com&amp;#x2F;appengine&amp;#x2F;docs&amp;#x2F;standard&amp;#x2F;python&amp;#x2F;imag...&lt;/a&gt;&lt;p&gt;The best part is, you call your image with specific parameters that&amp;#x27;ll do transformations on the fly. For example,
    &amp;lt;image url&amp;gt;&amp;#x2F;image.jpg?s=120
will return a 120px image. Appending -c will give you a cropped version, etc.&lt;p&gt;I really hope to see AppEngine get more love from startups as it&amp;#x27;s a brilliant platform, much more performant than it&amp;#x27;s competitors&amp;#x27; offerings. For example, I was previously a huge proponent of Heroku and upon comparing numbers, I realized AppEngine is way more performant (in my use case). I&amp;#x27;m so glad we made the switch.&lt;p&gt;If you&amp;#x27;re looking&amp;#x2F;considering to move to AppEngine, let me know here and I&amp;#x27;ll try my best to answer your questions.</text></item></parent_chain><comment><author>dang</author><text>Accusations of astroturfing or shilling are against the HN guidelines, so please don&amp;#x27;t comment like this here.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;newsguidelines.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;newsguidelines.html&lt;/a&gt;&lt;p&gt;The reason is that the accusation is false orders of magnitude more often than it is true—because people falsely assume someone else can&amp;#x27;t possibly be holding an opposing view in good faith—and false accusations damage the community.</text></comment>
<story><title>Moving The New York Times Games Platform to Google App Engine</title><url>https://open.nytimes.com/moving-the-new-york-times-games-platform-to-google-app-engine-e9337f2c9444</url></story><parent_chain><item><author>smn1234</author><text>The way you&amp;#x27;ve delivered this &amp;quot;experience&amp;quot; makes you sound like you either work for Google or were asked to make a sponsored statement - for credits or $.</text></item><item><author>neya</author><text>Hey community, let me share my experience with AppEngine. I work in a small firm, where we&amp;#x27;ve developed a massive Software Application comprising of 12 medium-sized apps. I went with Phoenix 1.3 w&amp;#x2F; the new umbrella architecture.&lt;p&gt;With AppEngine, the beauty is that you can have many custom named microservices under one AppEngine project and each microservices can have many versions. You can even decide how much percentage of traffic should be split between each of these microservices.&lt;p&gt;What&amp;#x27;s awesome is, in addition to the standard runtimes (Ruby, Python, Go, Java, etc.) Google also provides something called custom VMs for AppEngine, meaning you can push docker based setups into your AppEngine service, with basically any stack you want. This alone is a HUGE incentive to move to AppEngine because usually custom stack will require you to maintain the server side of things, but with Docker + AppEngine, zero devops. Their network panel is also very intuitive to add&amp;#x2F;delete rules to keep your app secured.&lt;p&gt;I&amp;#x27;ve been using AppEngine for over 4 years now and every time I tried a competitive offering (such as AWS Beanstalk, for example) I&amp;#x27;ve only been disappointed.&lt;p&gt;AppEngine is great for startups. For example, a lesser known feature within AppEngine is their real-time image processing service API. This allows you to scale&amp;#x2F;crop&amp;#x2F;resize images in real time and the service is offered free of charge (except for storage).&lt;p&gt;Works really well for web applications with basic image manipulation requirements.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;cloud.google.com&amp;#x2F;appengine&amp;#x2F;docs&amp;#x2F;standard&amp;#x2F;python&amp;#x2F;images&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;cloud.google.com&amp;#x2F;appengine&amp;#x2F;docs&amp;#x2F;standard&amp;#x2F;python&amp;#x2F;imag...&lt;/a&gt;&lt;p&gt;The best part is, you call your image with specific parameters that&amp;#x27;ll do transformations on the fly. For example,
    &amp;lt;image url&amp;gt;&amp;#x2F;image.jpg?s=120
will return a 120px image. Appending -c will give you a cropped version, etc.&lt;p&gt;I really hope to see AppEngine get more love from startups as it&amp;#x27;s a brilliant platform, much more performant than it&amp;#x27;s competitors&amp;#x27; offerings. For example, I was previously a huge proponent of Heroku and upon comparing numbers, I realized AppEngine is way more performant (in my use case). I&amp;#x27;m so glad we made the switch.&lt;p&gt;If you&amp;#x27;re looking&amp;#x2F;considering to move to AppEngine, let me know here and I&amp;#x27;ll try my best to answer your questions.</text></item></parent_chain><comment><author>sunsetMurk</author><text>or a passionate user who had a great experience?! I love finding solutions which require less &amp;#x27;square peg round hole&amp;#x27;. Unfortunately, rare these days when piecing together a stack w&amp;#x2F; the myriad of platforms&amp;#x2F;frameworks&amp;#x2F;etc.</text></comment>