Hi Denis -- My main reason was for embedding jetty as an ignite service was to have ignite manage jetty instance, the same it does for any other kind of service.
On Thu, Jun 4, 2020 at 3:30 PM Denis Magda <dma...@apache.org> wrote: > Clay, > > Do you have any specific requirements in mind for the ignite service + > jetty deployment? If possible, please tell us a bit more about your > application. > > Generally, I would deploy Jetty separately and use load balancers when > several instances of an application are needed. > > - > Denis > > > On Wed, Jun 3, 2020 at 3:20 PM Clay Teahouse <clayteaho...@gmail.com> > wrote: > >> Thank you, Denis. I'll research this topic further. >> >> Any recommendation for/against using jetty as an embedded servlet >> container, in this case, say, deployed as an ignite service? >> >> On Fri, May 29, 2020 at 11:22 PM Denis Magda <dma...@apache.org> wrote: >> >>> Clay, >>> >>> Just start your Jetty server and deploy as many instances of your web >>> app as needed. Inside the logic of those apps start Ignite server nodes >>> instances. Then, refer to this documentation page for session clustering >>> configuration: >>> https://apacheignite-mix.readme.io/docs/web-session-clustering >>> >>> Also, there were many related questions related to this topic. Try to >>> search for specific by googling for "session clustering with ignite and >>> jetty". >>> >>> Let us know if further help is needed. >>> >>> >>> - >>> Denis >>> >>> >>> On Fri, May 29, 2020 at 6:57 PM Clay Teahouse <clayteaho...@gmail.com> >>> wrote: >>> >>>> 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 <dma...@apache.org> 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 <clayteaho...@gmail.com> >>>>> 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 >>>>>> >>>>>
