We just released new capabilities in Skip to make reactive services scale easily and efficiently across machines. Skip’s core is a native reactive computation graph that minimizes unnecessary recomputation—great for real-time apps—but now you can also scale horizontally using a leader/follower architecture.
We’ve open-sourced an example service (yes, it's called hackernews) you can try locally or on Kubernetes. It supports seamless scaling via kubectl scale, with zero downtime and no changes to your backend logic.
We just released new capabilities in Skip to make reactive services scale easily and efficiently across machines. Skip’s core is a native reactive computation graph that minimizes unnecessary recomputation—great for real-time apps—but now you can also scale horizontally using a leader/follower architecture.
We’ve open-sourced an example service (yes, it's called hackernews) you can try locally or on Kubernetes. It supports seamless scaling via kubectl scale, with zero downtime and no changes to your backend logic.
Blog post with diagrams and code here: https://skip.dev/blog/dynamic-scaling
GitHub repo: https://github.com/skiplang/skip To try it:
Curious to hear your thoughts or feedback!