steepdawn on Nostr: I see. I just wonder if you truly run the whole "thing" (Websocket + Strom + LN node ...
I see. I just wonder if you truly run the whole "thing" (Websocket + Strom + LN node (presumably LDK/Greenlight/BreezSDK)
Strom is Typescript (I guess), and can run in AWS Serverless
https://aws.amazon.com/de/blogs/compute/building-typescript-projects-with-aws-sam-cli/
Websocket can natively be run via API Gateways
https://www.freecodecamp.org/news/real-time-applications-using-websockets-with-aws-api-gateway-and-lambda-a5bb493e9452/
And I guess(!) also the Lightning part of the code can be run by one of the AWS services. Presumably also AWS Serverless, if just using Greenlight/BreezSDK (bit i might be wrong)
That would mean you can deploy the whole Strom-as-a-Service stack serverless, and when a new CP/CP operator comes along, you presumably just edit some config somewhere to register it, and provision its own Websocket
Strom is Typescript (I guess), and can run in AWS Serverless
https://aws.amazon.com/de/blogs/compute/building-typescript-projects-with-aws-sam-cli/
Websocket can natively be run via API Gateways
https://www.freecodecamp.org/news/real-time-applications-using-websockets-with-aws-api-gateway-and-lambda-a5bb493e9452/
And I guess(!) also the Lightning part of the code can be run by one of the AWS services. Presumably also AWS Serverless, if just using Greenlight/BreezSDK (bit i might be wrong)
That would mean you can deploy the whole Strom-as-a-Service stack serverless, and when a new CP/CP operator comes along, you presumably just edit some config somewhere to register it, and provision its own Websocket