Architecture - Where you can stick your state
There is a lot of confusion, especially for newcomers to J2EE, regarding state and where and where not to put it. We examine the myth that stateless in the middle-tier is “always” better. This session focuses on the real issue of scalability in the enterprise: serialization.
“Distributed computing is the art of serialization.” Knowing when and where to hold state has one of the largest impacts on scalability. The session will look at architecture topology and the effect it has on complexity and scalability with a focus on state and state management. Subjects of clustering and stateless vs. stateful services will be scrutinized.
About Ken Sipe
Ken is a distributed application engineer. Ken has worked with Fortune 500 companies to small startups in the roles of developer, designer, application architect and enterprise architect. Ken's current focus is on containers, container orchestration, high scale micro-service design and continuous delivery systems.
Ken is an international speaker on the subject of software engineering speaking at conferences such as JavaOne, JavaZone, Great Indian Developer Summit (GIDS), and The Strange Loop. He is a regular speaker with NFJS where he is best known for his architecture and security hacking talks. In 2009, Ken was honored by being awarded the JavaOne Rockstar Award at JavaOne in SF, California and the JavaZone Rockstar Award at JavaZone in Oslo, Norway as the top ranked speaker.
More About Ken »