From PHP to Transactions

An airhacks.fm conversation with Ondrej Chaloupka (@_chalda) about:
RPG character generators with Turbo Pascal, Delphi and Visual
Basic. D&D, Pentium 100 and Atari 500 ST, the joy of
programming, the object oriented paradigm with Java 1.5 at
university, warehouse software with JBoss 5 and enterprise Java,
the first line of Java code was "public static void main", Java is
not the ideal language to start programming with, building Swing
apps at the University of Brno, studying computer science was hard,
computer theory at the university is actually useful, design
pattern overuse is an enterprise Java disease, some best practices
move to Java EE platform - there is not need to solve the already
solved problems, internship in Brazil with PHP and JQuery in 2009,
the main problem of early Java EE was slow deployments, starting at
RedHat as quality engineer for JBoss AS 7, quality insurance is a
great way of on-boarding, starting to work on transactions, most
PHP applications were built with "auto commit" transactions,
transactions are convenient, enhancing code coverage for the
transaction manager, fixing own bugs filed as quality engineer,
starting as narayana developer, narayana, arjuna and JBoss
Transaction Manager are the same bits, migrating narayana to
MicroProfile Long Running Action (LRA), building transactional file
system JCA connectorz, the narayana bootstrap with XML (timeout,
implementation, recovery, transaction log), transaction manager and
transaction recovery manager are the key parts, the transaction
recovery manager is needed to remember what the server did, XID vs.
Global ID, transaction context is stored in a ThreadLocal, joining
transactions with JPA EntityManager, UnitOfWork in EntityManager,
JDBC and XA transactions, a XA JDBC driver has to be exposed to the
TransactionManager, a local transaction can be directly managed by
the EntityManager, the XA / 2PC (two phase commit) protocol in
detail, EntityManager: transactions and flushing, XA optimizations,
Quarkus and Narayana, storing transaction logs in a central
database, @Stateless, @Transactional and UserTransaction, code
simplification with CDI and EJB, premature transaction optimisation
is the root of some evil, starting transactions at the boundary
layer, slower performance without transactions, in business
applications with some state you will always need something like
local transaction, thinking differently with NoSQL, Dr. Martin
Kleppmann (@martinkl) transactions, challenges with microservices
and transactions.

Ondrej Chaloupka on twitter: @_chalda, and the JBoss Trasactions,
Narayana, Arjuna blog