This is often overlooked and with the new SSR initiatives from the #frontend world more important to realize: a #serverless function that's always running is just an expensive server.
Does anyone know (or could point to) the theoretical or practical limit on the number of deployed #AWS#Lambda functions that an account can contain? I can't see the question answered anywhere.
Not concurrent executions; not provisioned capacity; not create-function-requests-per-second; not function versions ... but the number of uniquely named functions that can be deployed, possibly sitting unused, ready to be invoked, in an AWS account ... 🤔 #serverless
Pushpin decomposes real time web technologies (like #websockets into a request/response backend which works really well for #serverless and honestly most application stacks. Long lived connections are hard to manage near your app logic.
The GRIP protocol is straightforward and lower level than you'd expect.
They have recently released the #whitepaper for #fleekNetwork which not only has #IPFS but also decentralized edge CDN.
Most exciting of all is that they have a #Services concept that seems to allow for running your code on other people's nodes and getting a #crypto guarantee that the work was done!
#Netlify's new #Drop tool allows you to create a new website using #AI and have it automatically deployed to #theCloud.
"Simply describe the website you want to build not only will #chatGPT author the markup scripts and style sheets but it will deploy it to Netlify I for you too!"
moving from typescript to python for a serverless project, all I'm expecting is there but the level of convenience is not comparable. Any recommendations for starters? Chalice is not an option. As of now I'll be going with serverless.com and moto for mocking. #aws#Python#typescript#serverless
In 2009, #CommonJS was exactly what #JavaScript needed. The group took a tough problem and forced through a solution that continues to be used millions of times a day.
But with #ESM as the standard and the focus shifting towards cloud primitives — the edge, browsers, and #serverless compute — and CommonJS simply doesn’t cut it. ESM is a better solution for developers, as they can write browser-compliant code — and for users who get a better end experience.
I've tried #Fleek's products in the past; I deployed a site to #IPFS, but I needed a #backend where I could do things like connecting to #databases and #APIs. Then I tried out their #ICP deployments, but I found them to be limited, and ICP itself far too complicated for my #web2 brain.
#Palm#WebOS, at the time it was developed mainly for smartphones, had this rather simple approach of “give me your logins, I’ll build a unified local stream of all your interactions on social networks” and I sometimes think it’s time to bring that concept back. #activitypub but with translators/connectors where needed. #Serverless. Locally on your device.
Seeking advice on minimizing function and worker usage (Nuxt on Cloudflare Pages)
What I want to do:...