Kirk,
I think I was thinking all are doable but the focus is on the common use
cases of hot deployment and multi-tenancy. Now multi-tenancy doesn't mean
it has to be an multiple untrusted entities using the same cache, I simply
mean the need to host multiple "applications" in the same Geode cluste
What about hot-redploy only?
1.b) Hot-redploy variation
This is the case where the user wants to have only one realm of
"application code" deployed but be able to update application code and 3rd
party dependencies without restarting the server. For
example, one Function might use a 3rd party depe
Given that we are heading toward microservices architectures wherein
isolation of data to bounded contexts is of critical importance, I think
that the kind of multi-tenancy we're talking about here is on the decline.
We're probably well off going after single tenant or departmental grids for
now a
I have some questions from the previous discussion thread about adding in
some sort of application isolation feature to Apache Geode.
"application code" -- defined as a Function or plain old application code
that uses the Geode APIs including Cache and Region
There is more than one level of code
