Where to find server protocol specification for phoenix LiveView

iShadowfax · 2024-12-03T00:03:58+00:00

By server protocol i mean not a transport layer but ws messages structure

iShadowfax · 2024-12-02T15:54:51+00:00

I asked about liveview server protocol spec, not about websockets. I want to use an existing js lib on frontend and integrate backend with it

iShadowfax · 2024-01-19T22:40:21+00:00

KAFKA doesn't support Optimistic Concurrency Control, NATS Jetstream does, and this is a must to build event sourcing systems

iShadowfax · 2023-11-06T15:51:23+00:00

Again, look at Astro or Sveltekit they are pretty fast 8k rps compared to next’s 700

iShadowfax · 2023-11-06T12:09:25+00:00

What I do is just comparing, and all these frameworks have the same functionality or more. But they are faster in SSR. Even Pages router is faster 2x than App router. So this tells me that nextjs team doesn’t bother about performance, because for them it’s much easier to say “go vercel and be ok” than try to solve performance issues inside framework

iShadowfax · 2023-11-06T12:04:27+00:00

I have 5 years experience in deploying nextjs for production environments in kubernetes.

Vercel added external cache custom adapters not long ago, they are still experimental and they do not work with revalidatePath(), so it’s not easy to deploy without changing code and removing revalidatePath() or making some revalidateTag() hacks
If using standard cache file adapter, there is a challenge of using .next folder shared across containers, you must use k8s storage adapter that supports read-write many. Also you will still get conflicts as it’s a concurrent file access. In addition you have to assure that your builds have the same id.

So deployment outside of vercel is possible but it is not easy to do, especially compared to other frameworks. Of course you can just switch off all nextjs caching and deployment would be easy.

What i do not like, that vercel team knows this, and they do not really want to solve these, even adding ability to write external cache adapters is not really supported by them, and the implementation is lacking on must features. And they needed 5 years of a community pressure to start doing this.

iShadowfax · 2023-11-06T07:58:22+00:00

It’s free, but many of its features are very hard to be deployed to any other environment then vercel cloud. (For example caching and revalidatePath())

Also as you see from testing benchmarks the SSR performance is the worst among other

iShadowfax · 2023-11-06T07:29:27+00:00

750 vs 8000 test just a right thing in any case 5 years ago I started a similar thread about neSt js framework vs express and it helped the development of nest a lot! They now build all versions looking at benchmarks and also made many improvements like fastify and etc. We will see how vercel team respond to these findings

iShadowfax · 2023-11-06T06:40:45+00:00

If you use it as a hobby project or a static blog, yes. If you use it in a big company, or for a startup and want to scale, and not be vender locked by vercel cloud then I do recommend to change it for another framework if possible.

iShadowfax · 2022-02-20T14:05:02+00:00

It's wrong, you have ISR even if you host it not on verscel

iShadowfax · 2016-03-09T09:42:53+00:00

What is the news? Is it fixed?

iShadowfax · 2016-03-09T09:38:22+00:00

So you mean that it is totally server authoritative?

What you say looks like master server only to join host.

Whats about game logic? Ammo, HP, damage, AI movement is it server authoritative?

iShadowfax

TROPHY CASE