thank you Denis. If I want to go with the first option, how would I deploy jetty as embedded server? Do I deploy it as an ignite service? How would I do session clustering in this case?
On Fri, May 29, 2020 at 3:18 PM Denis Magda <[email protected]> wrote: > Hi Clay, > > I wouldn't suggest using Ignite's Jetty instance for the deployment of > your services. Ignite's Jetty primary function is to handle REST requests > specific to Ignite: https://apacheignite.readme.io/docs/rest-api > > Instead, deploy and manage your restful services separately. Then, if the > goal is to do a web session clustering, deploy Ignite server nodes in the > embedded mode making the sessions' caches replicated. Otherwise, deploy the > server nodes independently and reach the cluster out from the restful > services using existing Ignite APIs. This tutorial shows how to do the > latter with Spring Boot: > https://www.gridgain.com/docs/tutorials/spring/spring_ignite_tutorial > > - > Denis > > > On Fri, May 29, 2020 at 8:25 AM Clay Teahouse <[email protected]> > wrote: > >> hello, >> I understand that ignite comes with embedded jetty server. >> 1) Can I utilize this jetty server to deploy my own restful services >> (using Jersey implementation)? If yes, can you please direct me to some >> examples. >> Further questions: >> 2)How does the ignite embedded jetty work with regard to load balancing? >> Are there multiple instances of the embedded jetty server running behind a >> load balancer? In other words, can I invoke multiple instances? >> 2) How does this scheme work with web session clustering? >> 3) Would the ignite node run in server mode? >> 4) I want the jetty sessions access ignite caches (on the server side) as >> the data source for the data returned from the restful services. >> >> Any help and advice would be much appreciated. Thank you >> >
