Event sourcing starts with a question
Before choosing an event store, decide which questions your product needs its history to answer.
Notes from building, lessons in the details, and a closer look at what’s next. A journal for curious people who care about software.
18 pieces of writing
Before choosing an event store, decide which questions your product needs its history to answer.
The story behind LN Software, and why the company brings products, open source and new collaborations under one roof.
How to reach LN Software, what to include in a useful support request, and where public open-source reports belong.
Our portfolio separates active work from retired projects, including Dedicated IP and Lawyours, so visitors can see where LN Software is focused.
Explore our Go projects for event sourcing, Invoice Ninja integration and maintained llama.cpp bindings, with the upstream work clearly credited.
A short, concrete brief can expose the decisions that matter before a team invests in the wrong kind of progress.
Useful webhook integrations define identity, event meaning, delivery behavior and recovery before writing the handler.
A note on our property product's direction: clearer pre-bid research, a considered identity, and an honest account of what a report can tell you.
LN Software is opening conversations about focused consulting and software projects, starting with the decision or outcome that matters.
LN Software takes its name from Lena and Nina. That personal beginning gives the studio a simple reason to care about what lasts.
Source links become useful when readers can connect them to a claim, inspect their context and understand what remains uncertain.
Exports, clear account controls and an honest product status make software easier to trust throughout its lifecycle.
An invitation to discuss product collaborations and potential co-founder relationships, with room to test the fit before making commitments.
Our Confluence Cloud app puts text comparisons and patch visualisations into the documents where teams discuss their work.
Running inference inside an application changes the boundaries of the system. It also creates new responsibilities.
A useful fork explains its origin, compatibility promises and remaining limits as clearly as its new capabilities.
A timeout does not tell you whether a remote action happened. Reliable integrations have to account for that uncertainty.
A useful projection starts with the person reading it, including what they need to know about freshness and recovery.
Try a different search or explore all our writing.
Keep the good ideas coming. Follow the journal in your favourite RSS reader.
Subscribe via RSS