Thanks David!
1. If I have to create all the web services as a separate heroku apps,
how would I share the database instance between the more than one
services or apps like admin tools or crons?
While sharing a database between apps isn't officially supported, you could
have a way to expose an app's ENV['DATABASE_URL'] to other apps. This URL
may change periodicially, so you'd want to make sure you had a way to
reacquire the new one rather than hardcoding it.
Another way to accomplish similar functionality is to expose the data you
need as an API that is consumed by the other apps in your architecture.
I would prefer the API approach if the data set is NOT large in size.
ENV['DATABASE_URL'] approach doesn't seem very clean. I will have to
spend some time to explore these two.
2. If the consumer facing web-app needs to call other services within
the cloud to fulfill the request, do I have to use public address (may
be using CNAME or whatever) or can I have it route it within the
cloud?
Requests would need to be made to the public address (via the domain name)
as the hostname is what routes a request to a given site.
If I have to setup my own data center, I would create a network for
the production environment with firewall etc. And, the network would
have its own DNS/hostnames. Within that network if one app needs to
call a service, the number of hops are limited to within the network.
In the heroku environment, if one app needs to call another service
within the environment using public address (via the domain name),
what would be the number of hops before it gets to the service. Would
it route within the cloud? I am just concerned about the performance
and security.
Thanks!
Chandra
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.