Disadvantages for Brazilians to use the Google App Engine

Asked

Viewed 410 times

2

I’ve done some app and some testing with Google App Engine.

I’ve read about several of your limitations, and some of them are a little bit boring, but nothing that worries me too much, because as I intend to do something new, you already build thinking about the limitations.

Although not all limitations are necessarily bad things, example would be the lifetime of a request, which anyway, no should take a lot (even if it is ajax), as this is limited in other environments/servers, besides usability issues. Well that was just an example.

As I have worked with other types of databases (owner of the company or the language) that is not in the SQL style, Bigtable is also not so difficult to adapt. I know you have other options, but as far as scalability goes, Bigtable is the king. Of course not every type of app is easy or feasible to do with bigtable, but in the case of the app I want to build, this is also no problem.

But there are some items that bother me, worry a little, and would like opinions on the items, whether good or bad:

Price if in dollar, ie with the return of this exchange difference, that is very worrying.

Not having data center in Brazil, that is, however good the data center is, will always have a higher Leg than it was in Brazil, of course, there are many factors involved, and this can be good or bad.

Does anyone remember any further disadvantage?

Or would like to comment on any of the points mentioned?

Someone has experience telling about the Google App Engine?

python cloud

1 answer

4


Disadvantages in General

There are several disadvantages not only for Brazilians, but also for any developer who uses it, some of them are :

Apps by developer - 10

Time per request - 30 sec

Archives by App - 3,000

HTTP size - 10 MB

Datastore item size - 1 MB

Application Code Size - 150 MB

Even more so if you check the list of known problems of GAE,you will see that it is many,see in these topics talking about various problems encountered by GAE.

Other disadvantages are :

Developers have read-only access to the file system in the Google App Engine.

App Engine can only run a code called from an HTTP request (except for scheduled background jobs).

Users can upload arbitrary Python modules, but only if they are pure-Python; C and Pyrex modules are not supported.

Java applications can only use a subset (The JRE Class White List) of classes from the JRE standard edition.

Java applications cannot create new topics.

Disadvantages for Brazilians

Taking a look at the official Google App Engine documentation, API of the GAE, is more or less the following :

Write >> $0.10 per 100,000 transactions, in real is equivalent to 0.34 cents.

Read >> $0.07 per 100,000 transactions, in real is 0.24 cents.

OBS : Above are the cost of methods used, for example using 100 thousand operations with the method Write You pay $0.10 for GAE.

To see how much it cost the least in the matter of host on the part of GAE,I used their official service cost calculator,which can be accessed here.

Putting at least the upload requirements,gave in total $75,55.But by converting to real, R$257,66 to stay with the minimum requirements.

Detail,you pay monthly this amount,and this taking into account the value of the dollar compared to today,used this website to make the conversion and it uses on a daily basis the conversions, the value of the dollar can always increase as the reflection of the international market.

That is, the cost is much higher compared to host on the part of Brazilians, imagine with reasonable requirements of upload,how much would not leave.

To see the full documentation of the costs that GAE charges, here.

Completion

For me there are still more disadvantages than advantages for us Brazilians to use the Google App Engine, for not only economic factors but still there are other factors in development through itself. GAE is still new to certain requirements, only now has it been able to provide the basis for MySQLfor example, but even so, there is still much to improve, API are still limited to tasks that one wants often there is a good support for such.

  • 1

    "Apps by developer - 10", is this not a free account limitation? Even if it is not, just having more than one mobile phone, of course has the drawback of having more than one google account. I know that google does not care if the same person has more than one account, I for example have 2 GAE. I know said by the words of a google engineer himself, who gave a lecture in python brazil of Curitiba, a long time, but I think it’s still so.

  • 1

    A technical limitations, I know several, not all obvious, but this still would not be a big problem for the type of app I would like to do, I wanted to know more practical questions, which you just notice doing. Still very helpful your explanations, thank you.

  • 1

    Ah, do you have any practical experience with GAE, even if it is small? I understood your points and agree with most of them, but when one of the essential requirements is scalabidade, wouldn’t it pay? Type, by large capacity and facilitated & #Xa;to scale GAE applications?

  • 1

    @Juniorc-Sharp-Asp.Net Yes, in this area of scalability you pay to have improvements in your services. Because when it comes to request you can only have 500 requests per second, if you want more, you’ll have to pay.But there are other resources like easy-to-understand administration and reports from GAE that they make for you for free.

  • 1

    @Juniorc-Sharp-Asp.Net One of the real problems even with using GAE that any developer soon realizes is that as your site expands, you’ll have to spend more on the host issues and technical requirements to maintain your site.

Browser other questions tagged python cloud

You are not signed in. Login or sign up in order to post.