4 ms·
Specially interesting given other similar recent announcements, Google's per-second billing also covers: | "premium operating system images including Windows
by fhoffa 9y ago
Specially interesting given other similar recent announcements, Google's per-second billing also covers:
| "premium operating system images including Windows Server, Red Hat Enterprise Linux (RHEL), and SUSE Enterprise Linux Server"
(disclosure: I work for GCP)
- DannyBee 9y agoI'm completely unsure why that is worth special mention? (disclosure: I don't consider what I do to be work)
- rch 9y agoThat's the only helpful use of the disclosure line I've seen in a few years .. thanks.
- unshift 9y agomany employers request that employees provide a disclosure when discussing their products on social media
- TheIronYuppie 9y agoWe don't, but generally do it out of an abundance of caution. (disclosure: I work with the above two)
- deleted 9y ago[deleted]
- morgo 9y agoI think it's a pretty good policy. Fake reviews/astroturfing comments can hurt a brand quite severely. The riskiest situation of course is talking about a competitor's product (which we kind of are here). It doesn't have to sound like a legal disclaimer, but its nice to identify your relationship to the product may have (even subconscious) bias.
- deleted 9y ago[deleted]
- boulos 9y agoThe AWS announcement left the licensed things as hourly granularity. Disclosure: I helped write this blogpost ;). (And I consider what Danny does to be work)
- wasd 9y agoHey fhoffa, got a second for a GCP question? Am I calculating App Engine Flex pricing wrong? From what I can tell, it starts around ~$40 / mo (1 vcpu, 512 mb ram) which is 5x over comparable Heroku hobby dyno instance?
- Jabbles 9y agoDon't they have a free tier for hobbyists?
- jpatokal 9y agoThere's one for App Engine Standard, but not for Flex. (Disclaimer: I work at GCP.)
- merb 9y agoWhat bugs me most for App Engine Standard is that under Java I need a custom ThreadFactory, when I want to use Standard Threads and use a Google Api. I need to copy the Environment into every new thread I create. Can't they fix that somehow? (Currently, if you want to call App Engine APIs (com.google.appengine.api.*), you must call those APIs from a request thread or from a thread created using the ThreadManager API.) (https://cloud.google.com/appengine/docs/standard/java/runtime-java8 https://cloud.google.com/appengine/docs/standard/java/runtim...) Basically the line is even incorrect since I can use my own ThreadFactory if I'm on a Request/Backend Thread and clone the Environment and copy it into each Thread.
- thesandlord 9y agoNo you are not wrong, and we are working on it. It's going to be a lot more powerful (3.7 GB, 1 full core) than a hobby Dyno, but definitely overkill for testing. Until then, here is my shameless plug: https://medium.com/google-cloud/three-simple-steps-to-save-costs-when-prototyping-with-app-engine-flexible-environment-104fc6736495 https://medium.com/google-cloud/three-simple-steps-to-save-c...
- wasd 9y ago