i don't think it's too far, distributed nanoservices are what cloudflare workers are designed around

it's just a shame that remix has a monolithic approach, which makes things difficult

I mean, Workers do perform measurably better in a monolith structure, rather than as nanoservices(as evidenced by Service Binding cold starts).

service binding cold starts shouldn't be any different to normal workers?

That's what I mean. Once a script is warm, it is warm. If you have to dive into a service binding, then you are subject to a second/third/fourth set of cold starts.

If your script is a monolith, you only cold start once.

now I want to benchmark svc binding startup

Another issue with that approach is eventually you hit the limit of workers granted it is pretty large 😛 and deployment when you have many workers is much harder because cloudflare doesnt have targetable versions like AWS does on lambda so you might get in a weird state where some workers are updated and others arent

Like, break a script up when it gets too large, but until then, try to keep it in as few as possible.

service environments would fix that when they come back

w.r.e targetable

but... I have no idea when they'll come back

I kinda miss them already

If service environments do fix that it would be nice yeah but not here rn 😛

more specific to this scenario, service bindings can target a specific service environment on the bound worker

they're very critical for deploying microfrontends

but i don't know if the API validates that at publish time

i.e can you depend on Worker A Env A in Worker B Env A if Worker B is published before Worker A?

probably not

Im talking about not only targeting a specific environment but a very specific deploy version inside the env

you only need two environments tho: green and blue 😅

environments for CF im pretty sure is more dev staging prod not for blue/green

but not sure as I never used them

Maybe you could create a new environment for every different deploy and retarget but that is a lot

You could use WfP to target a specific version.

if you have WfP you could but that also adds more to cold starts

cold starts here really means very little, shouldn't focus too much on them

on a remix app it's likely going to be 1-5% of the page load time

the whole point of the github issue you linked said cold starts to be fair 😛

time to benchmark svc binding cold starts