Neos Conference 2020: Event Sourced Content Repository - the current status

Transcript

1. The Event Sourced Content Repository: The Current Status
2. Introduction
3. Content Repository Asset Storage Fusion Flow Framework Neos Neos UI
4. NodeDataRepository NodeInterface Doctrine ORM "naive" Database Schema Identity Map Fusion / FlowQuery Read API Write API Dimension handling NodeData Not well de fi ned slow for big node trees, performance hard to predict hard to reproduce bugs (sometimes) orphan nodes sometimes possible advanced features hard to integrate Masking of deleted nodes (Shadow Nodes) Workspace Shine Through Node Type Management
5. Fusion / FlowQuery Read API Write API Node Type Management TraversableNodeInterface NodeInterface Commands NodeDataRepository Doctrine ORM "naive" Database Schema Identity Map Dimension handling NodeData Masking of deleted nodes (Shadow Nodes) Workspace Shine Through
6. Fusion / FlowQuery Read API Write API Node Type Management TraversableNodeInterface NodeInterface Commands Dimension Space layer Content Stream / Workspace layer Doctrine ORM "naive" Database Schema Identity Map
7. Doctrine DBAL Runtime Cache Fusion / FlowQuery Read API Write API Node Type Management TraversableNodeInterface NodeInterface Commands Dimension Space layer Content Stream / Workspace layer "naive" Database Schema
8. Dimension Space layer Content Graph Event Store Commands Content Stream / Workspace layer Fusion / FlowQuery Read API TraversableNodeInterface NodeInterface Node Type Management Write API well de fi ned, sound concept optimized for move and other complex cases basis for advanced features great performance Doctrine DBAL Runtime Cache
9. It's a big change behind the scenes.
10. Content Repository Asset Storage Fusion Flow Framework Neos Neos UI
11. Why are we doing the rewrite?
12. Model modify read classical Database Architecture Database
13. update projections append events Event Sourced Architecture Events "modify" read* Event Store e1 e1 Node properties were updated e2 Node was created e3 Node properties were updated e4 Workspace was created
14. "Model", e.g. with Doctrine ORM update projection read the "model" Projections DB Tables
15. Projections can be rebuilt DB Tables Empty DB Tables apply event 1 DB Tables apply event 2 apply event 3 apply event 4 apply event 1000
16. write side read side (projections) Event store (DB Table) Content Graph Commands Events Workspace Changes (soft) constraints …
18. We know what has happened in the past.
19. We have built a sound, consistent concept for main interactions like workspaces, content dimensions, the node tree, hidden nodes, ...
20. Proper History and Undo
21. Editing Noti fi cations
22. Synchronization
23. YOUR ideas!
24. already four years in the making
25. December 2016: First Workshop
26. September 2017: ES CR Workshop Kiel
27. March 2018: ES CR Workshop Dresden
28. May 2018: Neos Conference Hamburg
29. May 2019: Neos Conference Dresden
30. What did we do since last year?
31. Workspace handling implemented nested workspaces support cleanup routines for stale data
32. Implemented Missing Features implemented reference properties document tree performance FlowQuery fi nd() implementation started workspace module node:repair kickstarted groundwork for Import / Export
33. Stabilization adjusted Neos.UI 
 Neos.EventSourcing fi xes & tests Backend Caching Integration Copy/Paste Support lots of small fi xes in the Neos backend
34. Neos.EventSourcedContentRepository: 17 000 LOC (including comments) Neos.EventSourcedNeosAdjustments: 14 000 LOC (including comments) quite stable CR Core layer beta quality changes needed because of API adjustments in CR to be merged into core at some point alpha quality
35. Neos.EventSourcedNeosAdjustments: 14 000 LOC (including comments) You can help!
36. Compatibility Layer ... emulating parts of the old Node Context api your Fusion code mostly still works :)
37. Standalone Usage Support we made it a library, which runs even 
 without Flow 
 works in e.g. Symfony
38. Experiments started Graph Database backend
39. More Realistic Examples demo site docs.neos.io with Event Sourced Content Repository
40. Demo Time
41. How do we work?
42. Bastian + Sebastian + Bernhard Christian + David
43. my personal brain nut 4 hours of coding 1 hour of thinking 1 hour of discussing new insights
44. join us!
45. Neos.EventSourcedContentRepository Neos.EventSourcedNeosAdjustments do the heavyweight discussions read the stack trace fi x a condition (rarely) adjust the underlying API
46. Neos.EventSourcedNeosAdjustments: 14 000 LOC (including comments) Support us!
47. Roadmap
48. demo site docs.neos.io neos.io site A Prototype site B we're here :)
50. we're here we need to be here
51. Covid-19
52. Fundraiser 50.000 - 100.000 € We didn't get this organized.
53. Spent last year 10.000 € from the Neos Core Team budget. Lots of "hobby evenings."
54. It's all about the money? No! I and others are pushing the topic forward, regardless of funding. 
 We won't make any promises when it's done.
55. Neos.EventSourcedNeosAdjustments: 14 000 LOC (including comments) Support us!
56. How can I help?