An ack to Pub/Sub is a delete command, not a proof of processing. With the workflow engine in the ack path and a correlation that rejects, the place of the ack decides between standstill and data loss. The complete tutorial: nack with dead-letter topic, transactional inbox, a relay without the ordering trap, plus a decision table.
An external contractor is to work on the pricing engine of a tool shop but must not see the payment integration. Permissions apply at repository level, which settles the question. This tutorial performs the split step by step with the history intact, shows the trap of directories renamed long ago and what still gets forgotten on migration day.
An online tool shop ends expired promotions overnight. The job reports 412 hits and the shop keeps selling at the promo price. Three annotations on the repository interface are behind it: two reach deep into Hibernate, one does nothing at all. The complete tutorial on readOnly, @Modifying and where the transaction boundary belongs. As of Spring Boot 4.
Fourteen line items of a goods receipt stopped dead, with no error and no incident. A signal only reaches whoever is already waiting when it is thrown, and an asynchronous step sat right before that. This tutorial rebuilds the case with Flowable 8, shows it in a test, repairs the stuck instances and replaces the broadcast with an addressed message.
Six teams, the same storage, a ticket every time. This tutorial builds a platform API from scratch with Crossplane 2.3: provider, ProviderConfig, the first managed resource, then XRD and Composition, until a team orders its own storage with eight lines of YAML. Including the parts that hurt: deletion, drift and more than 900 resource types.
The decisive logic often sits next to the code rather than inside it: in the process model, in the job setup, in the configuration. How to test those promises with Flowable 8 and Spring Batch 6, and how to turn the quality scenarios from arc42 chapter 10 into executable tests.
On a greenfield there is nothing yet, and hardly any estimate gives the foundation a realistic size. Why that happens, and what order to start in.
A stack is an ordered chain of pull requests where every layer builds on its predecessor and only the foot of the chain touches main. GitHub supports this natively since 30 July 2026. A complete tutorial covering gh stack, the cascading rebase and the condition that comes with it.
The site was blank, the backup could not be restored, and the fastest route was a full rebuild. This article walks through the cold start step by step: detach the domain, delete every file and the database, reinstall, deploy, plugins, legal pages and cookie banner. With the acceptance checklist, the reason why design is the hardest part in WordPress, and the honest limits of the approach.
