5 ms·
> My goal is to be totally unable to SSH into everything that powers my app That sounds like a nightmare to me, and I'm not even a server guy, I'm a backend gu
by paganel 8y ago
> My goal is to be totally unable to SSH into everything that powers my app
That sounds like a nightmare to me, and I'm not even a server guy, I'm a backend guy only managing my personal projects.
> I'll pay Amazon $N/month to do that for me, all that matters is the product.
I don't want to pay Amazon anything, I want to pay Linode/Digital Ocean 5 or 10 or 20 dollars per month and I can do the rest myself pretty well. My personal projects will never ever going to reach Google's scale and seeing that they don't bring me anything (they're not intended to) I'm not that eager to pay an order a magnitude more to a company like Amazon or Google in order to host those projects.
- staticassertion 8y agoAs someone tasked with protecting infrastructure, devs not being able to SSH into production is a godsend.
- scaryclam 8y agoThere's a difference from devs not being able to ssh in due to access restrictions and devs not being able to ssh in because it's not a feature of the service. I actually agree that not having unilateral access to the production system is a good thing. But not being able to have anyone able to be granted access, even for a limited time, is neither productive or safe.
- hackerpacker 8y agoso, what is to stop them from running code from the app?!? Who do you call when something breaks? Do you expect the dev to not be able to log in and investigate at 3am or whenever? I mean if you can't trust your dev team, or the procedures surrounding them, you are kinda screwed.
- staticassertion 8y agoTo be clear, the issue isn't about trusting developers in prod. It's about limiting access to prod as an avenue for attackers who will be looking to get in there and exfil sensitive data. Nothing to do with trust of devs.
- everdev 8y agoCloud providers have generous free tiers, so many personal projects pay $0. However, I'm in the same boat. I'd rather pay $20/month to DO and risk my site going down in a DDoS attack than having a REST endpoint basically tied to my credit card and hoping Amazon blocks all the malicious traffic.
- jcadam 8y agoYep, keep your stuff portable and you can always migrate to AWS/Azure/etc. later if your personal project should turn into something bigger.
- leeoniya 8y agoit's astounding how much a $20 linode can handle (as a web host) with a proper software stack and performance-minded coding. but companies throw money, hardware and vendor lock-in at problems way before commiting to sound engineering practices. i have a friend who works at an online sub-prime lender, says their ruby backend does hundreds of queries per request and takes seconds to load. but they have money to burn so they just throw hardware at it. they spend mid-five figures per month on their infrastructure and third party devops stuff). meanwhile, we run a 20k/day pageview ecommerce site on a $40/mo linode at 25% peak load. it's bonkers how much waste there is. i think offloading this stuff to "someone else" and micro-services just makes you care even less about how big a pile of shit your code is.
- 72deluxe 8y agoAnd we just thought the frontend of websites and services was bad. Seems the insanely bad coding and ignorance of speed and performance goes all the way to the backend too! Disappointing.
- DylanBohlender 8y agoOne of the things I'm most grateful for as a programmer was the ability to learn a lot of performance-minded backend design principles within the Salesforce ecosystem. Salesforce was always brutally unforgiving in terms of the amount of I/O it would let you do per transaction, which led me to become much more aware of how those things worked under the hood, and had the effect of teaching me how to better design my code to fit within the limits. When you can't use more than a couple seconds of CPU time per transaction, or you have a fixed and spartan heap size for a big algorithm, you learn good habits real quick. I imagine a lot of engineers today haven't had the experience of working within hardware limits, hence all the waste everywhere.
- leeoniya 8y ago> When you can't use more than a couple seconds of CPU time per transaction hmm, i guess that explains why salesforce is universally known for being slow; 2 seconds is an eternity. we deliver every full page on the site within 250ms from initial request to page fully loaded (with js and css fully executed and settled). images/videos finish later depending on sizes and qtys.