1 / 35

JSR 350 State Management

Overview and update JSR Expert Group. JSR 350 State Management. Overview. Background Why a JSR for State Management Key concepts Relationship to other standards Example API Demo Timeline Q & A. In a nutshell….

dwayne
Télécharger la présentation

JSR 350 State Management

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. Overview and update JSR Expert Group JSR 350 State Management

  2. Overview • Background • Why a JSR for State Management • Key concepts • Relationship to other standards • Example API • Demo • Timeline • Q & A

  3. In a nutshell… JSR-350 is an API for finding and using state management services to save and retrieve data independent of the storage method.

  4. Background • Standard formed through JCP (2.8  2.9) • Oracle lead (Mitch Upton), participation from Red Hat, IBM and independents • Expert group activated April 2012 • Some existing proprietary solutions in WebLogic, Tomcat and JBoss

  5. Requirements • “…develop an API that applications and JavaEE containers can use to offload the responsibility of state management into third party providers with different quality of service characteristics” (JSR) • Standardize existing APIs • Support a wider variety of data representations (JSON, XML, name value) • Expand storage mechanisms (NoSQL, Graph DB, In Memory)

  6. Use Cases • Cloud - loose coupling of apps to state management facilities • Mobile - cross platform state handling • Integration - Transfer of state between platforms • Capability based provider querying • Transient data e.g. session state • Non relational data e.g. JSON, XML, JavaScript

  7. Value of State Management (over Existing APIs) • Independent storage mechanism – not specific to DBMS, file, etc. • Access service by capability instead of low level configuration • Manage state with strongly or weakly-typed approach • Pluggable marshalling of types

  8. Contrast to Persistence APIs • JPA • Strongly typed • Assumes relational storage • JDBC • SQL access but must manage ORM, integrity, transactions • Deep technical knowledge • EJB • Complex • Java I/O • Complex, low level

  9. Design Goals • Store and retrieve state independent of mechanism • Modular and consistent implementation • Capability based matching of client and provider • Support innovation and the cloud • Easy to use interfaces – user, provider, platform

  10. API to Multiple Providers JEE Client JSE Client State Management API Built-in Provider Custom Provider 3rd party Provider

  11. Key Concepts • State (State Container) • State Connection Factory • State Connection • State Container • State Map • Capability

  12. State • Unit of data • Uniquely identified within a scope • Persistent for a business period • Used by web apps, web services, JSF, CDI • Currently implemented via in memory, file, database, cluster

  13. State Container • Container for a user-defined state value that allows a State Management provider to present and track system-level details about the value • An instance of State contains a single user-specified value

  14. State Connection Factory • Create one or more State Connections based on required capabilities • Associated to single provider • Typed e.g. Java class (…probably)

  15. State Connection • Connection to state management services provided by some provider • Expose capabilities • Contains configuration • Controls the transaction – either local or distributed using JTA • Use directly or to get a StateMap

  16. State Map • Exposes only entries with a given key and value type in StateConnection • Convenience interface - clients deal directly with user-specified key and value types, no need to see containing structures such as Key and StateContainer • Contains: • globally unique key • value of a user-defined type • tracking information • Key • User defined + GUID • Values • Java type (e.g. Person class) • Streams? • XML?

  17. Capability - QoS • Behaviour offered by a provider • Durability • Transactions • Isolation and concurrency control • Supported by configuration • Described by a unique name

  18. State Classes State Management Registry State Connection Factory 1 0..* 1 0..* State Connection 1 0..* 1 State Container 0..* 0..* State Map 1

  19. Getting a Connection State Management Registry Client Application State Connection Factory State Connection Find State Connection Factory Create Get State Connection Create State Connection

  20. Using a StateContainer State Container Client Application Key Dog State Connection new (“fido”, “Sheperd”) createKey(fido.getUniqueName(), String.class, Dog.class) create fidoKey Store put(fidoKey, fido) create StateContainerfidoState get(fidoKey) Retrieve fido copy

  21. Using a StateMap State Map Client Application Dog State Connection new (“fido”, “Sheperd”) getStateMap(String.class, Dog.class) create Store StateMapdogMap put(fidoKey, fido) get(fidoKey) Retrieve fido copy

  22. Standards View 350  347 (107) Client State Management API (350) Data Grid API (347)

  23. Standards View 347  350 Client Data Grid API (347) State Management API (350)

  24. Standards View 350 &347 Client State Management API (350) Data Grid API (347) State Management API (350)

  25. Roles • Provider • Implement the specification • Innovate with new capabilities • Administrator / Developer • Configure the state connection factory • Make a State Connection available • Developer • Use State Connection and State to accelerate development

  26. Example - StateConnection

  27. Example - StateContainer

  28. Example – get/put StateContainer

  29. Get a StateMap

  30. put/get a Dog/Person

  31. Demo

  32. Design Debates • Typing • Strong versus weak • Is StateMap necessary / desirable?

  33. Next steps • Expected milestones • How to provide feedback

  34. Q & A

  35. Further Information • Java State Management Wiki http://java.net/projects/java-state-managemen • JavaOnepresentation http://java.net/downloads/java-state-managemen/2011-J1-Java-State-Management-v2.ppt • The spec http://www.jcp.org/en/jsr/detail?id=350

More Related