github-starred/Socio
2
0
Fork 0
mirror of https://github.com/Rolands-Laucis/Socio.git synced 2026-05-15 14:15:57 -06:00
Code Issues Projects Packages Wiki Activity Actions

readme

Browse source
This commit is contained in:
Rolands 2026-02-22 09:17:18 +01:00
parent d4d15540ec
commit 5771c188c8
4 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -12,7 +12,7 @@
* [Simple Documentation](https://github.com/Rolands-Laucis/Socio/blob/main/Documentation.md)
---
This lets you write SQL in your frontend code, that automagically refreshes on all clients when a resource is changed on any (optionally) connected DB. Additionally, create any generic JS variables on your server to be realtime synced across all clients using "Server Props".
This replaces the REST API paradigm in your app, by letting you write SQL in your frontend code, that automagically refreshes on all clients when a resource is changed on any (optionally) connected DB. Additionally, create any generic JS variables on your server to be realtime synced across all clients using "Server Props".
Agnostic of framework, build tool, server lib and SQL database. Requires Node.js >= 16 LTS.
@ -80,7 +80,7 @@ const res = await sc.SetProp('color', '#ffffff'); //this will rerun ^ the sub, i
## Does it scale? ⚖️
Currently the performance is neglegable for small projects. I havent stress tested yet, but I optimize my data structures and procedures. Current estimate is about 100 concurrent users should be a breeze on a cheap Linode server. I expect your backend DB to be set up properly with table indexing and caching.
Currently the performance is negligible for small projects. I havent stress tested yet, but I optimize my data structures and procedures. Current estimate is about 100 concurrent users should be a breeze on a cheap Linode server. I expect your backend DB to be set up properly with table indexing and caching.
[According to this blog](https://medium.com/nativeai/websocket-vs-http-for-collecting-events-for-web-analytics-c45507bd7949) WebSockets are much more network traffic efficient than HTTP at scale.

4
core/README.md
View file

@ -12,7 +12,7 @@
* [Simple Documentation](https://github.com/Rolands-Laucis/Socio/blob/main/Documentation.md)
---
This lets you write SQL in your frontend code, that automagically refreshes on all clients when a resource is changed on any (optionally) connected DB. Additionally, create any generic JS variables on your server to be realtime synced across all clients using "Server Props".
This replaces the REST API paradigm in your app, by letting you write SQL in your frontend code, that automagically refreshes on all clients when a resource is changed on any (optionally) connected DB. Additionally, create any generic JS variables on your server to be realtime synced across all clients using "Server Props".
Agnostic of framework, build tool, server lib and SQL database. Requires Node.js >= 16 LTS.
@ -80,7 +80,7 @@ const res = await sc.SetProp('color', '#ffffff'); //this will rerun ^ the sub, i
## Does it scale? ⚖️
Currently the performance is neglegable for small projects. I havent stress tested yet, but I optimize my data structures and procedures. Current estimate is about 100 concurrent users should be a breeze on a cheap Linode server. I expect your backend DB to be set up properly with table indexing and caching.
Currently the performance is negligible for small projects. I havent stress tested yet, but I optimize my data structures and procedures. Current estimate is about 100 concurrent users should be a breeze on a cheap Linode server. I expect your backend DB to be set up properly with table indexing and caching.
[According to this blog](https://medium.com/nativeai/websocket-vs-http-for-collecting-events-for-web-analytics-c45507bd7949) WebSockets are much more network traffic efficient than HTTP at scale.

4
core/package-lock.json generated
View file

@ -1,12 +1,12 @@
{
"name": "socio",
"version": "1.15.13",
"version": "1.15.14",
"lockfileVersion": 2,
"requires": true,
"packages": {
"": {
"name": "socio",
"version": "1.15.13",
"version": "1.15.14",
"license": "MIT",
"dependencies": {
"@msgpack/msgpack": "^3.1.2",

2
core/package.json
View file

@ -1,6 +1,6 @@
{
"name": "socio",
"version": "1.15.13",
"version": "1.15.14",
"description": "A WebSocket Real-Time Communication (RTC) API framework.",
"main": "./dist/core.js",
"type": "module",