Earlier quoted context omitted.
For what it’s worth when I was TL I would regularly hang out on discord and answer questions for R2. I believe the team still does that and the community itself also answers a lot of questions. Now that I TL Workers KV I do the same in that chat room. There’s also the community forums although I find it’s harder to stay on top of those personally. Not trying to say our paygo support is as good. Just saying for those…
The Cloudflare Discord is where it's at.
Storage on Vercel
131–140 of 144 posts
Re: Storage on Vercel
#132Am I the only Luddite who Deploys Go app containers. Pick a cloud. Use whatever they offer. Deploys static JS to cdn Calls it a day. I really do not understand these tools. Who is using them? I’ve built and worked on apps used by millions of people. Really don’t understand where the benefit is or if people are just over complicating basic things to extract money from chump developers?
Re: Storage on Vercel
#133Am I the only Luddite who Deploys Go app containers. Pick a cloud. Use whatever they offer. Deploys static JS to cdn Calls it a day. I really do not understand these tools. Who is using them? I’ve built and worked on apps used by millions of people. Really don’t understand where the benefit is or if people are just over complicating basic things to extract money from chump developers?
And now that your app is using one of these frameworks, you probably need some sort of API for whatever. There's a lot to be said about designing a REST api just being exporting an JS function in a file in a /api folder or whatever. If you are already using a hosted option for these frameworks it's an incredibly simple solution that doesn't require to you mess around creating a new project, making a docker image, going to a different cloud provider and giving them your credit card, etc. And depending on your scale that might genuinely be cheaper than running a container 24/7 on a public cloud.
Re: Storage on Vercel
#134Earlier quoted context omitted.
You will get better customer support from Vercel. Cloudflare gives almost zero customer support if you are pay-as-you-go plan.
For what it’s worth when I was TL I would regularly hang out on discord and answer questions for R2. I believe the team still does that and the community itself also answers a lot of questions. Now that I TL Workers KV I do the same in that chat room. There’s also the community forums although I find it’s harder to stay on top of those personally. Not trying to say our paygo support is as good. Just saying for those…
Re: Storage on Vercel
#135Am I the only Luddite who Deploys Go app containers. Pick a cloud. Use whatever they offer. Deploys static JS to cdn Calls it a day. I really do not understand these tools. Who is using them? I’ve built and worked on apps used by millions of people. Really don’t understand where the benefit is or if people are just over complicating basic things to extract money from chump developers?
Do you deploy just the JS to a CDN or a whole website? I wanted to do something similar, throw a static website on a CDN and use a Go API as its backend. But unsure how to get around CORS in a reliable way.
Re: Storage on Vercel
#136I'm wondering why vercel chose upstash vs cloudflare kv store? I've worked on very large deployments of cloudflare workers + kv store and the performance is amazing (and pricing). It would seem to me that upstash would add hops/latency vs cloudflare kv store?
Doesn't Cloudflare KV have to be used with Cloudflare Workers?
Re: Storage on Vercel
#137Earlier quoted context omitted.
They've looked at Postgres.js ( https://github.com/porsager/postgres ) before — wouldn't mind if they enabled those other cases in the same way. Also, node-postgres is ripe for sql injections because you just concatenate strings yourself when using it...
> node-postgres is ripe for sql injections because you just concatenate strings yourself when using it... Why the heck would you do that? I guess for any library that accepts SQL, someone might concatenate strings rather than use the parameter handling.
Re: Storage on Vercel
#138Earlier quoted context omitted.
> node-postgres is ripe for sql injections because you just concatenate strings yourself when using it... Why the heck would you do that? I guess for any library that accepts SQL, someone might concatenate strings rather than use the parameter handling.
The things I've seen because people don't want to learn an ORM's (or similar tech) API.
Not sure what ORMs have to do with it. They do include a safe parameter substitution mechanism, but so do typical SQL-based clients.
Re: Storage on Vercel
#139Earlier quoted context omitted.
They've looked at Postgres.js ( https://github.com/porsager/postgres ) before — wouldn't mind if they enabled those other cases in the same way. Also, node-postgres is ripe for sql injections because you just concatenate strings yourself when using it...
The examples on https://node-postgres.com/features/queries clearly show how to use parametrized queries. Of course you /can/ concatenate strings, no library in the JS land will prevent you from doing that. But the examples are pretty clear how to do it correctly.
Re: Storage on Vercel
#140Earlier quoted context omitted.
The things I've seen because people don't want to learn an ORM's (or similar tech) API.
I mean that node-posgres doesn't encourage anyone to include parameter values through string concatenation, at least no more than porsager or other SQL-based clients. Not sure what ORMs have to do with it. They do include a safe parameter substitution mechanism, but so do typical SQL-based clients.