1 / 9

Open J2EE Session Cluster

Open J2EE Session Cluster. December 2013. Agenda. Drivers Existing products Description Technology choices Demo Plan. Drivers. Current architecture at Penn has dedicated servers for applications Generally an app gets 3-10 app servers Traffic is not constant

keita
Download Presentation

Open J2EE Session Cluster

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Open J2EE Session Cluster December 2013

  2. Agenda • Drivers • Existing products • Description • Technology choices • Demo • Plan

  3. Drivers • Current architecture at Penn has dedicated servers for applications • Generally an app gets 3-10 app servers • Traffic is not constant • During the night or during certain times of year, servers are idle

  4. Drivers (continued) • AWS auto-scales • The Elastic Load Balancer uses monitoring (cloud watch) to scale up or down for certain thresholds • The ELB uses sticky session for our applications • Scaling up is not problem (existing sessions stay put) • Scaling down might be an issue (if there are sessions on the machine which will be terminated)

  5. Existing products • J2EE session replication • Tomcat has this • Multicast (inconvenient for multi-availability zones) • Not sure it scales well (other institutions I have talked to haven’t had good experience with it and don’t use it) • Other software add-ons didn’t look appealing

  6. Description

  7. Technology choices • Small Java filter, with few dependencies • Interfaces can customize various parts of the flow • Storage interface to S3 (Amazon Web Service Simple Storage Service) • AWS Elasticache might be better, but that is only available from EC2 (?) • AWS Dynamo DB was a candidate though items can only be 64kB • Could be in application database

  8. Demo • See movie

  9. Plans • Handle logout (delete session) • Ability to limit sessions for app or user? • Roll into AWS app in early 2014

More Related