- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Josh Durbin
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
Google’s App Engine Changes Pricing Model
Tuesday, May 10, 2011
This is Google parlance for it’s time to start making money.
As an IT services firm we have often had to overlook the GAE for projects due to the relatively narrow-scope of software design architecture the GAE is built to accommodate. The announcement today is a welcome change for Google’s PaaS. Much of the business-class features found in the GAE4B are being rolled into GAE and enforced SLAs.
The downside to all of this is in order to provide the enhanced functionality Google is changing the pricing model of GAE dramatically making it very similar to the pay-for-what-you-use model Amazon Web Services employs. Free apps will now be more restricted in their free resources and paid apps now have a monthly fee on top of usage fees.
This change in pricing model doesn’t go into effect until later this year but it brings a warning for all companies looking to deploy applications to the cloud. Providers can change their pricing model at any time and you must be prepared for it. Unlike on-premise software where a change in pricing often results in either sticking with a current software version or hardware appliance and foregoing upgrades while alternative are considered, cloud vendors may not give you such latitude.
We have always believed strongly in having a cloud deployment strategy that takes vendor migration into consideration. If you haven’t considered a multi-vendor cloud strategy then perhaps now is the time.
- Descriptive JMX Beans in AEM/CQ
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6