5 ms·
Google's App Engine is pretty much a for-profit API. And now they've announced a change in their pricing scheme, which if true, would change App Engine from pa
by bad_user 15y ago
Google's App Engine is pretty much a for-profit API.
And now they've announced a change in their pricing scheme, which if true, would change App Engine from pay-what-you-use to same-as-amazon-aws-but-pricier scheme, which makes it hugely expensive for a large portion of devs that have built on top of App Engine. And migrating away from App Engine is a total pain in the ass.
I truly hope that the blog-post missed important details or that they'll keep providing the old option too (i.e. paying per cpu-hour instead of instance-hour).
I know App Engine was beta, but people have built on it expecting instability in the implementation, not in its pricing scheme. I mean, come on!
- mcdaid 15y agoSee https://groups.google.com/forum/#!topic/google-appengine/ob-kMuDAAqc/discussion https://groups.google.com/forum/#!topic/google-appengine/ob-... Clarifies that you will be paying per instance hour, instead of cpu. Nothing is in concrete yet, if there is enough outrage amongst users maybe they will change their tune.
- nhoj 15y agoI never liked app engine. To me it seemed like you have to lock yourself into google as a vendor because your application has to be designed for app engine.
- kkowalczyk 15y agoI never liked Linux. You have to lock yourself into Linux APIs because your application has to be designed for Linux. I never liked relational databases. You have to lock yourself into SQL because your application has to be designed for SQL. I never liked python. You have to lock yourself into python because your application has to be designed for python.
- borism 15y agoI never liked IT anyway. Shit has to be designed and stuff. Why can't we all be friends and blossom like flowers in the fields?
- natep 15y agoNone of those are examples of vendor lock-in. Linux, sql, and python all come from many different vendors. If you were using, say, Debian, SQLite, and IronPython, and they all exploded, you could switch to alternatives pretty easily, I think.
- prodigal_erik 15y agoRelying on a service hosted by a third party is fundamentally different. Nobody, not even Torvalds or van Rossum, could throw a switch and shut down your Linux boxes or your Python interpreter, so any needed migration to an incompatible system can happen at your convenience.
- borism 15y agohave you tried migrating to Python 3.0 yet?
- georgemcbay 15y agoIrrelevant to the grandparent's point because your Python 2.x interpreter isn't going to stop working at the whim of an outside party.
- saurik 15y agoThis argument come up often, but makes no sense as it ignores the fact that software rots. I cannot keep running Python 2.x indefinitely without maintenance because knowledge of its flaws will slowly escalate until it is a security risk to keep operating it. If this doesn't happen to the tool itself, then it will happen to one of its critical dependencies, like an old version of SQLite it requires, or the previous generation of OpenSSL. Projects like Python, that simply don't care about maintenance costs of things that rely on it are simply being naive: they are pretty much saying "yes, you invested a ton of time into building code for Python 2; but those days are over: we, at some random shifting date in the future, are going to drop support for this, so if you want to get security updates to it, or hell: even upgrade to a newer version of Ubuntu with minimal pain, you now need to drop everything you are doing and reread all of that code to update it for our seemingly arbitrary changes, retesting the whole thing in the hope of finding any regressions you introduce; that, or go off-grid, maintaining this code and related infrastructure yourself". Seriously? Imagine if Linux 2.6.100 decided to drop support for socket(), because it is (truly) a painful API to support multiple transport layers with; /even if/ they said "dude, you can still just type socket_old, and we have a crazy preprocessor that hopefuly, if your code is obvious enough, does this search and replace for you", would you still be able to take their dedication to being a platform seriously?
- deleted 15y ago[deleted]
- w43l 15y agoadd to that, google blocks access to what ever countries they want
- njharman 15y ago> expecting instability in the implementation, not in its pricing scheme. I mean, come on! Really, really? Come on, these very same concerns (pricing, it's beta) were/are brought up regularly. If you choose to ignore warnings/recommendations and use GAE that's your fault.
- mike_esspe 15y agoI somehow missed the new pricing model. It looks like my bill will skyrocket 2-3 times to over $2000/month. They explicitly tell, that old customers will be forced to move to a new pricing scheme. I wonder why there weren't a rage on HN front page about that? I regret, that didn't choose AWS EC2 in the beginning.