Show HN: Shuttle – Build and ship backends without writing infrastructure files

I use shuttle to deploy some side Rust projects for my web facing parts. I love it.<p>They are also planning to allow you to host it yourself via a docker setup, in your basement or cloud. For now I’m just doing it via their service and gladly pay for it.<p>If you’re well versed into DevOps related activities you might find it odd that there’s a need for it. But personally I’m a father of 3 kids, have been a developer and and hacker for last 12 years or so, and while I could do AWS, gcloud or a VPS myself, I honestly rather spend that time on my product then infra worries. So far I haven’t experienced any issues with them and they are very friendly folks, always ready to help. They’ll also be at EuroRust next week.<p>If you’re like me someone who likes to develop stuff but not so much the deployment side of things, then honestly this is nice.<p>There’s honestly no lock-in:<p>1. You’re service (project) can easily be converted into a regular project, as shuttle is in code only visible in a minimal way, so you can fairly easily refactor it out of your project the day you want to switch away 2. And like I said they’ll allow to self host soon enough.<p>So maybe you can give it a try. Might be the accelerator you need to help you start a project &#x2F; business idea. Even if just to get you started.

Infrastructure from code is the least exciting development in the evolution of ops I&#x27;ve seen.<p>Helping manage complexity -- great. Pulumi, Terraform, the CDK, all of these infrastructure as code tools help manage complexity.<p>Hiding complexity behind a DSL, via comments attached to methods intermingled with code or annotations -- not great.<p>Some of these implementations are my business logic -&gt; your DSL via annotations or comments -&gt; &lt;Some other IaC DSL&gt; -&gt; CloudFormation -&gt; AWS. At some point the returns are diminished as you add more layers vs. the cost of operating what&#x27;s generated and trying to debug issues.

Seems ironic that you’d use rust to “build fast”. My impression is that Rust is more about building things safe&#x2F;correct and efficient, with developer productivity being lower relative to other modern languages.<p>That said, the “infrastructure-from-code” idea is interesting. I’m not a big fan of coupling your code to your infra, but I’m intrigued by the idea of inferring infra dependencies from existing application code.

From my experience with Rust, there is nothing fast about developing with it.

I&#x27;ve been surprised at how much I like Rust for backend work, but looking at the read me I have no idea what the case for this tool is. What do you use it for?

If you like the concept but prefer Go over Rust for backends, check out Encore [1]. Disclosure: I&#x27;m one of the founders.<p>[1] <a href="https:&#x2F;&#x2F;encore.dev" rel="nofollow noreferrer">https:&#x2F;&#x2F;encore.dev</a>

Without infrastructure files means polluting your code with vendor specific lines. I&#x27;m not sure how much better that is.<p>I&#x27;m not so keen on a single language only SaaS either. How many companies only deploy code in a single language?

&gt; Is Shuttle Secure?<p>&gt; We build and deploy every project in its own container. This gives you safe isolation from other users and all the other projects that are owned by your account.<p>So that&#x27;s a &quot;no&quot;. Containers are not strong security boundaries. Probably good enough between projects owned by your own account, but definitely not for between other users.

Now this is how you turn a language mainstream.

Not sure if being so opinionated about Rust is a good idea, but very cool nonetheless. Looks well done, excited to tire kick it.<p>Curious how you see this stacking up against things like Pulumi?

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

We do a bit the same at windmill.dev except for python and typescript and we parse the parameters directly from the signature without needing to use macros&#x2F;annotations. I wonder if the same could not have been done here where the macro would have been as a build processor.

My brain read this as “Build Back, Ends Fast.”<p>I thought trends were changing so quickly I now miss them before I even know about them. Glad I still have a few years left of semi-keeping pace

interviewed the CEO on the OSS founder podcast earlier this year :)<p>full interview (38min): <a href="https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=GBT7yp17P4Y">https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=GBT7yp17P4Y</a><p>highlights (10min): <a href="https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=TVco_9E9no8">https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=TVco_9E9no8</a>

Good luck competing with AWS! went great for my serverless platform startup (and everyone else..)

Maybe the title should specify &quot;rust backends&quot; or &quot;rust applications&quot;

The easy done right ! Rust + Postgres on a stateful server for CRUD apps.

Oh, “build backends fast”.

Is there anything like this for the Python&#x2F;Django world?

Yes, let&#x27;s have even more of people just writing code and not knowing anything about how anything works! Just what we need more of.

HN bingo card for the comments thus far:<p><pre><code> [x] mentions Rust [x] mentions Go [x] misunderstanding the word DevOps [x] compares product to Heroku [x] &quot;I just want to write code and make&#x2F;run a product and not know how that works&quot; [x] something about scaling [x] the solution to any problem is to write more code</code></pre>