I guess what I want to know is if all of my applications(or even all
GAE apps) shares the same DataStore and if it is possible or desirable
to internally be able to query content from one another without the
need of making an external request.
Fabricio C Zuardi
>Splitting your app into multiple services that are isolated seems like a good architectural decision
Service 1 has 5 minutes of down time a month on average.
Service 2 has 6 minutes of down time a month on average.
Service 3 has 15 minutes of down time a month on average.
Your Site on 3 services has 26 minutes of down time a month on average.
Sound like a good architecture?
Fetches to other apps are just as expensive as fetches across the web.
Fetches to the new back end instances may not be.
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
I would say If you're writing your apps to be modular, and not doing
crazy stuff, then a vulnerability in the chat module shouldn't result
in data exposure in another module (especially if you're not using
URL Fetches to another app actually can be much more efficient than
URL Fetches across the web.
Overall I'd say you might be adding a ton of complexity for little
gain though. Is writing the chat portion as a reusable module not
Makes for great modular code.
Tracking the cost of each… Load tester and the functions you are running. I routinely write GAE apps that all they do is run calls to see how much money the other apps cost in a clean room.
Real world cost analysis you are right is harder if everything runs on the same account, but really is the cost of your website based on the cost of running chat? I assume you are running chat for community building, so you kind of just put that in the bottom line until you get to a certain size.
Remember that every time App1 Fetches from App2 you pay 22 cents a Gigabyte of data. That’s likely to be more than the money you would save by deciding chat costs too much. :-)
If you write all of your modules as asynchronous AJAX and the data is in silos, then separate apps is not a bad thing. Because no part is actually dependent on the other.
I usually prefer to write small 'library' type modules that I can
include in my projects. But, like Brandon said, if the other service
is interacted with via AJAX calls and shares no data with the rest of
the app it probably doesn't matter (beyond any potential cross-domain