Funding Request: My work - Neos 9 Stabilisation - 2026

The Neos Project Finances & Fundraising
1

Hi dear Neosianer,

Our beloved event sourced Neos with its beautiful content graph needs some new inertia. Since start of April - and throughout the sprint - i have had new ideas and worked continuously on improving the Neos CR to make it more viable in medium to large projects.

It’s already May now and just days ago i stumbled into another rabbit hole and found ways to deal with our rare publishing race condition.

In this time i have spend more than 80 hours on these CR stabilisations. Excluding the sprint.

Now i have laid out all possible paths and am in the process in finalising the changes as well as coordinating the merges and wrapping up everything into something release-able.

For an overview i can tell that i have been actively working on the following topics:

Publishing race conditions :person_running:

Must be the weather. But since a few days i have been able to reliably reproduce the sort of error that haunts us: Lock wait timeout exceeded; try restarting transaction and Content stream "..." is closed

… over the last year i had not made much progress

But now i was able to gather more insights and I started on working on many solutions to prevent the case as well as on a new event-store commit implementation to ensure integrity at core level.

Love for our event store :heart:

Our event store was last released one year ago. Through my profiling and new-found demands for the event store i have prepared a few changes. Also the code is slightly modernised and CI is now up and running again.

Ill plan to tag a few releases in the core and adapter as per the plan Release plan May 2026 - Version::next() *g

Publishing / workspace experiments :test_tube:

Publishing is currently slow because it creates expensive workspaces. And many expensive workspaces slow down the system. That is status quo of Neos 9.0. Inspired by the discussion to cleanup old user workspaces i experimented and created a PoC of a few of our other ideas. These experiments are now closed but laid the foundation for something better and bigger …

Fast core publishing and workspaces :high_voltage:

As it seems right in time for Neos 9.2 there will be a new concept for the DBAL graph adapter. Content stream layers. With layers a workspace can be created with cost of almost nothing. This is required to speed up our login. Also during publishing or rebase the we heavily profit from fast copying.

If you’re interested in that i recommend to look at my beautiful graphs here.

image
image1181×801 64.2 KB

Bugfixes :bug:

In the process of mowing through the CR i found a handful of bugs which i have fixed

Other :playground_slide:

Aside from this i have done a little more but this is not part of the funding request.

For example i have cleaned up parts of our behaviour test suite TASK: Use commands instead of events in behaviour tests, TASK: (Slightly) improve workspace / publishing test coverage and TASK: Sane visibility constraints in behaviour tests

Also i try to help coordinating the PostgreSQL adapter Beta 1.0 requirements · Issue #2 · neos/contentgraph-postgresqladapter · GitHub

And i am thinking already over the next optimisations FEATURE: “Synchronised” workspaces | Fork content stream after first write

Funding :pretzel:

I like to finish what i have started - 30 hours - and also apply for a partial funding of the time invested - 50 hours.

I would like to apply for funding of 8.000 € - covering 80 hours

  • Yes
  • No
0 voters

The voting closes Friday the 22nd of May 2026 20:00 CET

2 Likes
2

Thank you so much for your work, that will help every user <3

1 Like