golem15/summercms
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(architecture): add performance and scaling page compared to PHP-FPM

Browse Source
This commit is contained in:
Jakub Zych
2026-10-01 19:20:46 +02:00
parent 2fc5eac6d5
commit 4103d95a1a
3 changed files with 94 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/setup/coming-from-wintercms.md
View File

@@ -10,7 +10,7 @@ SummerCMS keeps the parts of WinterCMS that make a plugin developer productive.
What changes is everything that depends on PHP at runtime. Plugins are Go packages compiled into one binary, so there is no plugin directory scanned at boot and no runtime autoloading. Magic methods, dynamic properties and behaviours give way to Go interfaces and composition. SummerCMS is headless: it serves a JSON API and the admin SPA, and the frontend is a separate application that calls that API.
This page maps the concepts. To see them applied to one plugin from start to finish, follow [Porting a plugin](porting-a-plugin.md), which takes an `acme/blog` plugin with a model, migrations, a route, a backend controller and a console command to SummerCMS.
This page maps the concepts. To see them applied to one plugin from start to finish, follow [Porting a plugin](porting-a-plugin.md), which takes an `acme/blog` plugin with a model, migrations, a route, a backend controller and a console command to SummerCMS. To see how the single-binary process model changes speed, memory and scaling compared with PHP-FPM, read [Performance and scaling](../architecture/performance-and-scaling.md).
## Concept map