deploy_feedback VS shuttle

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.

Moreover, I especially like where Rust is right now in the web space. It really feels like there’s a lot of smart people working on the next generation of web development tools - it feels like the place to be. There are a range of great open-source web dev tools that are just reaching critical levels of maturity. Axum, which I used to build Prodzilla, feels ready for out of the box web dev, and is crazy-performant, as I write about later. More recently available is Loco, a Rails-like framework for building web applications in Rust that's picking up steam. And in dev-tooling and hosting there’s Shuttle, a 1-line hosting solution for Rust backends.

cargo-shuttle is Shuttle's own CLI for interacting with the Shuttle platform. Within the src folder, you will be able to get a better sense of how you can organise your folders/files for a larger CLI project for a live service. There is also use of async here with tokio, so if you're interested in learning how to get started with using clap with async services (for example setting up an async client for a database service), this would be a perfect opportunity to learn to do so!

https://github.com/shuttle-hq/shuttle/tree/main/services/shuttle-axum https://docs.rs/shuttle-axum/0.34.1/src/shuttle_axum/lib.rs.html#1-78

It would be great if there are some kind of code snippet on the README that really demonstrate the "ship backends without writing infra" feature that I think is one of the unique feature of shuttle. I remember seeing one on the official website (https://shuttle.rs) that left me impressed.

Shuttle is currently accepting entries for a competition, with the best projects being featured at our booth at the [EuroRust](eurorust.eu/) conference this year.

Reading here https://shuttle.rs may be nice to try for the future.

At Shuttle, we've teamed up again with Stefan Baumgartner, the organizer of Rust Linz and author of 'Typescript in 50 lessons', to host a free workshop titled "Rust for Javascript Developers: Building apps that utilize LLMs".

The community being built at https://shuttle.rs is extremely open and welcoming. I’ve yet to do anything on the main code base, but I’ve helped with the docs.

At Shuttle we’ve teamed up with Stefan Baumgartner, the organizer of Rust Linz, to create a newsletter series that takes a slightly different approach towards learning Rust.