Do you prefer local environments or cloud environments?

I think the major downside of having your important functionality in public cloud (usually not the case, but) is that when a major part of the cloud goes down (say, the previous Amazon issue), your services no longer (properly) work.
Of course, there's private cloud, hybrid cloud...
Pros and cons.

As someone having downside for a week I'll just shut my mouth.

But I hope we learnt something from the recent AWS outage. Cloud fine, but maybe not centralizing it to one provider.

I worked for huge cloud provider several years and wrote provision software but still there lessons to learn. Couldn't login to repair mailserver bevause out of no where 2fa requiring my mailserver to work. My god. I my defense it never was 2fa and I would not have chosen it.

Also, cloud or not, depends on service. Back in the day, they said never do email bevause of complexity (still a thingy) but also the spam. Well, my molodetz address never has spam while mentioned everywhere and it just runs clamav. I use mailcow for that, could recommend.

Repository, for sure, beautiful software available for that.

Edit: shutting mouth failed hard.

I don't host my own mail, I use https://mxroute.com/ and can add as many domains as I want

@BordedDev This is totally an ad. jk

@CaptainRant Is and endorsement and ad? 🤔

@chatgpt ?

Green environments with grass and trees

@BordedDev I've hosted my own e-mail for decades. It's ... gotten a lot more complicated, and totally not for the weak.

https://battlepenguin.com/tech/...

In general I try to self-host all my own stuff. I always prefer local development. The current company I'm in, a lot of the developers point to a cloud hosted dev for Mongo, Kafka, etc.

I finally spent some time getting my local Mongo working, but have held off on Kafka. There are some guides. The Confluent Cloud Kafka sucks ass. 30 minute timeouts, even if you're actively doing stuff in the web interface .. which is horrifically slow.

I never want to be in a startup again, but if I did somehow get drafted into one: #1 thing would be running everything on our own servers. Either on fiber or co-located. Do not tie yourself to AWS/Azure/any other garbage provider.

@BordedDev From my studies in Sales, it's part of the funnel. :D

@djsumdog For sure, years ago I was asked to make a gmail competitor, got damn close as well ;P but it's why I just went with the easier option. The emails aren't that important to me (and if I need access I'll just move the records to a new provider) Though I should probably setup a backup.

And yeah always dev local as well, but host in the cloud. But will always avoid anything atlassian related because of those performance issues. The intended benefit of cloud is failover, and we were always meant to run on multiple providers