Live data from Hacker News

Moving The New York Times Games Platform to Google App Engine

open.nytimes.com

151–152 of 152 posts

Re: Moving The New York Times Games Platform to Google App Engine

#151
post #85

Hey community, let me share my experience with AppEngine. I work in a small firm, where we've developed a massive Software Application comprising of 12 medium-sized apps. I went with Phoenix 1.3 w/ the new umbrella architecture. 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 percent…

The way you've delivered this "experience" makes you sound like you either work for Google or were asked to make a sponsored statement - for credits or $.

Accusations of astroturfing or shilling are against the HN guidelines, so please don't comment like this here.

https://news.ycombinator.com/newsguidelines.html

The reason is that the accusation is false orders of magnitude more often than it is true—because people falsely assume someone else can't possibly be holding an opposing view in good faith—and false accusations damage the community.

Re: Moving The New York Times Games Platform to Google App Engine

#152

Earlier quoted context omitted.

Why wouldn't it be "fair"?

Because a key-value store is a foundamentally simpler data structure (it's an hash) than a relational database, which tracks the relations between different data types. If you make an advanced use of the key-value store, you have a lot of logic in the application (for example to key management, cascade operations between related data...) which a relational database should do for you. It's not fair because there is a…

Dynamo is not a k-v store.
Post reply on HN