Proactive insights, news and tips from Oracle WebLogic Server Support. Learn Oracle from Oracle.

  • August 27, 2020

Jakarta Tech Talk Tuesday Sept 1 - Managing State in Elastic Microservices

Will Lyons
Senior Director, Product Management

On Tuesday, September 1, at 11AM EDT Aleks Seovic will be presenting a virtual Jakarta Tech Talk on "Managing State in Elastic Microservices".   You can register for this event here. Jakarta Tech Talks are both conference based and virtual webinars dedicated to the discussion and discovery of Jakarta EE and broader Cloud-Native Java technologies.  The abstract for this particular event is given below.

Scaling stateless services is easy, but scaling their stateful data stores, not so much. This is true whether you are using an “old fashioned" relational database, or one of the popular, “modern" KV data stores, such as MongoDB or Redis.

In this presentation we will discuss some of the issues with state management in elastic microservices today, and look into how Oracle Coherence, with its Helidon and Eclipse MicroProfile integration, provides a better alternative you can use tomorrow.

This will be a technical presentation by an architect who has deep technical understanding of microservices and data grid technologies, and real-world experience building and deploying mission-critical applications.   Aleks' talk will include a demo showing how Java microservices can be easily scaled, including flexible scaling of the data store used by the microservices, using an example you can evaluate yourselves following his talk.   The example is built with Helidon 2.0  and Coherence Community Edition  announced in June.  Both Helidon and Coherence can be used with WebLogic Server to build and evolve applications, either on-premises or in the cloud, so the content will be relevant and thought-provoking for WebLogic Server users.  Register today! 


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.