Security is becoming another architectural question that I need to address before the application grows much further. At first sight, an event-planning application may not appear to require particularly sophisticated security. It is not an online banking system. It is not controlling industrial machinery. It is not intended to store payment-card numbers or authentication secrets for thousands of Internet users. But that does not mean its data is harmless. An Event Document may contain names, telephone numbers, email addresses, postal addresses, attendance information, relationships between people, meal choices, special requirements, notes and potentially other personal information entered by the organiser. Depending on the event, the sensitivity could increase considerably. A corporate event might contain executive or customer information. A political event could reveal associations between people. A private celebration may contain home addresses and telephone numbers...
Based on a LinkedIn post originally published on 8 April 2026 Performance in my home-lab platform is the result of architectural choices rather than one isolated optimisation. The system does not depend on a single exceptionally fast disk or one configuration parameter intended to solve every workload problem. Instead, the design combines: memory-backed read caching through ZFS ARC; storage distributed across several back-end nodes; a dedicated storage network; asynchronous handling where the required write semantics permit it; SSD-backed staging for temporary I/O pressure; and separation between client-facing and back-end responsibilities. The objective is not maximum performance in one synthetic benchmark. It is stable, explainable behaviour across mixed workloads and during ordinary background activity. Peak throughput is useful. Predictable throughput under changing conditions is operationally more valuable. The client sees one service, not the back-end complexity HG000009 presents...