deploy_feedback VS neon

Hey all, Andy from the Deno team here. We're excited to share with you Deno Subhosting, an easy way to extend your platforms functionality by securely running untrusted JavaScript written by your users.

When we first launched [Deno Deploy](https://deno.com/deploy) in 2021, we were surprised at the volume of requests from companies about getting access to the APIs needed to run Deno Deploy. Many companies wanted to give their users the ability to write custom logic in their app, but setting this up in the cloud presents security concerns and a ton of infra work/maintenance.

We realized that there was an opportunity for Subhosting to solve a larger problem, which is allowing companies to easily and securely run custom code written by their users, without the hassle of maintaining said infrastructure.

Though we do have a few subhosting customers (Netlify being one of them), this launch makes our Subhosting product self-service, so any development team interested in extending their platform via their users' custom code can do so by [signing up](http://dash.deno.com/subhosting/new_auto) and [reading our docs](https://docs.deno.com/deploy/manual/subhosting). We have [an updated pricing model for Subhosting](https://deno.com/deploy/pricing?subhosting) as well, including a generous free tier fit for kicking the tires and building a proof-of-concept.

We'd love to get your feed back. Have you ever talked to your co-workers about allowing external devs to "have at it" with your platform? What would it look like to unlock the final 10% for your top customers? How have you approached this problem in the past?

Thanks for reading and the Deno team will be responding to comments!

[Read the announcement blog post.](https://deno.com/blog/subhosting)

That means we don’t need to transpile the Typescript code to ESM or CJS. Currently, only Deno Deploy can run your Typescript function out of the box. However, in order to keep the code small, we still need some sort of bundling. Luckily, Bun is also a bundler 😉

What type of apps do you code for your day-job? (I program for fun and curiosity, so that is why I ask that lame question.)

Do you use node.js? Deno is brought in part by the Node.js creator, Ryan Dahl, who wanted to fix/improve a lot of things he didn't like in node.js.

They also have "Deno Deploy" (with a free tier) to run your code on different servers scattered throughout the globe: https://deno.com/deploy

One of the reasons I love the `deno` executable is you can use `import` statements in your code and then tell `deno` to merge everything into a single .js file. I would then take that and publish it to Cloudflare Workers. I know you can do this with node.js and a bunch of tools, but it is so much simpler with `deno`.

The online version of DocTrack is hosted through Deno Deploy and is accessible here.

It runs on https://deno.com/deploy which runs on gcp at the moment but my understanding is that the underlying cloud provider could change at any time.

For deployment Deno offers it's own service, Deno Deploy:

https://deno.com/deploy

Disclaimer: Haven't used it yet.

Deno functions. Its different than docker containers that auto scale. https://deno.com/deploy

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110

Is any work being done to fix this? Or is this out of scope currently?

One of the valuable features of Solid Start is that you can use so-called "adapters" to completely change the output into something deployable basically everywhere that serves pages and with quite a lot of options: there are adapters for amazon web services, cloudflare pages and workers, deno deploy, netlify, standard node server (the default), vercel, and static deployment - the latter allows us to build something that we can put on github pages.

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:

https://github.com/neondatabase/neon/issues/4989

If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.

Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.

To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?

Neon is an open source and cloud-native serverless database platform that focuses on simplicity and ease of use. It supports Postgres databases and offers built-in features like bottomless storage, autoscaling, and branching.

For MySQL, we've got PlanetScale, and for PostgreSQL, there's Neon.

8. https://neon.tech/As you might know not one tool fits all, I still have strong preferences for the following. It helps me get going faster and get things done right first time and helps in ease of maintenance.

Language: Typescript.

Migrated away when they removed the free tier, ended up using https://neon.tech/

Cool! At Neon[0], I work full time on our custom postgres proxy[1]. It's a very nice protocol to work with, although our usecase is quite a bit more complex compared to the ideas presented in the post.

Neon databases scale to zero, so the proxy needs to spin up databases on the fly. The proxy doesn't do that but it knows if the databases is running and asks our control plane to schedule it if it isn't. It's a fun service to maintain.

The biggest pain is error handling. Postgres is really bad for error messages and codes. The only available code we can use is usually protocol violation...

[0]: https://neon.tech/

Neon - PostgreSQL

For those looking for alternatives check out https://neon.tech/, https://turso.tech/ and https://developers.cloudflare.com/d1/.

Neon is an open-source serverless Postgres offering.