How to use sagas in Java?

Video tutorial on using sagas to maintain data consistency in a microservice architecture
29 August 2017   3727

The microservice architecture structures an application as a set of loosely coupled, collaborating services. Maintaining data consistency is challenging since each service has its own database to ensure loose coupling. To make matters worse, for a variety of reasons distributed transactions using JTA are not an option for modern applications.

In this talk Chris Richardson describes an alternative transaction model known as a saga. You will learn about the benefits and drawbacks of using sagas. Chris describes how sagas are eventually consistent rather than ACID and what this means for developers. You will learn how to design and implement sagas in a Java application.

Chris Richardson is a developer and architect. He is the author of POJOs in Action, which describes how to build enterprise Java applications with frameworks such as Spring and Hibernate. Chris was also the founder of the original, an early Java PaaS for Amazon EC2. Today, he is a recognized thought leader in microservices.

Oracle to Publish Critical Patch Update

In the the freshest update, a total of 334 vulnerabilities were eliminated in such products as Java SE, MySQL server, VirtualBox and other 
15 January 2020   103

Oracle has published a scheduled release of its Critical Patch Update, aimed at resolving critical issues and vulnerabilities. In the January update, a total of 334 vulnerabilities were eliminated.

Java SE 13.0.2, 11.0.6, and 8u241 have fixed 12 security issues. All vulnerabilities can be exploited remotely without authentication. The highest level of danger is 8.1, which is assigned to the serialization problem, which allows compromising Java SE applications by transmitting specially designed serialized data. Three vulnerabilities have a severity rating of 7.5. These problems are present in JavaFX and are caused by vulnerabilities in SQLite and libxslt.

In addition to problems in Java SE, vulnerabilities have been disclosed in other Oracle products, including:

  • 12 vulnerabilities in the MySQL server and 3 vulnerabilities in the implementation of the MySQL client (C API). The highest danger level 6.5 is assigned to three problems in the MySQL parser and optimizer. Issues resolved in MySQL Community Server 8.0.19, 5.7.29, and 5.6.47 releases.
  • 18 vulnerabilities in VirtualBox, of which 6 are of high severity (CVSS Score 8.2 and 7.5). Vulnerabilities will be fixed in VirtualBox 6.1.2, 6.0.16 and 5.2.36 updates, which are expected today.
  • 10 vulnerabilities in Solaris. The maximum severity rating of 8.8 is a locally exploited issue in the Common Desktop Environment. Of the problems with a severity rating of above 7, local vulnerabilities in the Consolidation Infrastructure and the file system can also be noted. Issues resolved in yesterday's Solaris 11.4 SRU 17 update.

Learn more at the official blog