I'm currently working on a project that need to be dynamically scaled on demand according to the need.

My question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but I don't know how to proceed with spring context. Do i have to merge in one single context shared by all client application, or initialize one context by application.

I plan to use Scala Akka actors on Spring service, but I can't be persuaded by the solution of using one context exposed by actors. All of the rest of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapp by user profile to scale according user role (admin, enduser). But the only thing is Spring Context for business operations.

I'm currently working on a project that need to be dynamically scaled on demand according to the need.

My question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but I don't know how to proceed with spring context.

I plan to use Scala Akka actors on Spring service, but I can't be persuaded by the solution of using one context exposed by actors. All of the rest of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapps by user profile to scale according to user role (Eg. admin, enduser), however the only thing is Spring Context for business operations.

Question: Do I have to merge in one single context shared by all client applications or should I initialize one context per application?

I'm currently working on a project that need to be dynamically scaled on demand according to the need.

My question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but I don't how to proceed with spring context. Do i have to merge in one single context shared by all client application, or initialize one context by application.

I plan to use Scala Akka actors on Spring service, but I can't be persuaded by the solution by using one context exposed by actors. All of the est of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapp by user profile to scale according user role (admin, enduser). But the only thing is Spring Context for business operations.

I'm currently working on a project that need to be dynamically scaled on demand according to the need.

My question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but I don't know how to proceed with spring context. Do i have to merge in one single context shared by all client application, or initialize one context by application.

I plan to use Scala Akka actors on Spring service, but I can't be persuaded by the solution of using one context exposed by actors. All of the rest of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapp by user profile to scale according user role (admin, enduser). But the only thing is Spring Context for business operations.

I'm currently working on a project that need to be dynamicaly scaled on demand according to the need.

My Question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but i don't how to proceed with spring context. Do i have to merge in one single context shared by all client application, or initialize one context by application.

I plan to use Scala Akka actors on Spring service, but i can't be persuated by the solution by using one context exposed by actors. All of the est of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapp by user profile to scale according user role (admin, enduser). But the only thing is Spring Context for busines operations.

Thanks in advance,

Thibault NORMAND.

https://i.sstatic.net/0ysv7.png

I'm currently working on a project that need to be dynamically scaled on demand according to the need.

My question is about scaling spring context. My web application has a classical multi module core (service, persistence, domain), which use use by client application (webapp, api).

The user end application could be clustered, database too, but I don't how to proceed with spring context. Do i have to merge in one single context shared by all client application, or initialize one context by application.

I plan to use Scala Akka actors on Spring service, but I can't be persuaded by the solution by using one context exposed by actors. All of the est of the application is built with event driven techniques (Spring events are produced by the service layer).

I already built different webapp by user profile to scale according user role (admin, enduser). But the only thing is Spring Context for business operations.