erkken

It's not memory intensive at all - just CPU bound

I have a very cpu intensive application in Rust, that is able to use all cores given to it.

I am thinking about going for the Epyc 7502p with 32 cores but having a hard time knowing if the Threadripper counterpart with 32 cores would be better given its higher frequency.

Guess it is very hard to answer but which one would you go for? Will the threadripper perform much better?

I'm from Sweden and biked NY to SF a few years ago. During the two months it took I never locked my bike (didn't brought a lock at all). Just a related a anecdote ;)

Just switched to AWS from DO after 5 years. DO was working great, but needed a more managed solution (am very familiar with the sysadmin, but just wanted to reduce workload) so went with AWS Fargate and happy with it so far.

I think In 99% of the cases, the costs, work and effort by far outweighs possible benefits.

As the sole dev in my company, I have spent last few weeks to look at other solutions to DO as well. I can work it out fine as is, it's just that nowadays I am getting more and more security questionnaires sent by customers and it would be such a relief to just say that the security of the platform is managed by someone else.

Have been looking at beanstalk but no. Now its between app engine and heroku. Question on heroku: It feels a bit weird they not support hardware 2fa, doesn't it?

Do you have any other insight to give me on your transition?

I cycled from NY to SF 2015, with a detour to Chicago. I've done lots of bike touring in other parts of the world, but would say US is one of my top countries for bike touring!

I would say 99% of SUV owners do not need an SUV.

Oh, their DDoS protection was one of the reasons we were thinking about moving away from DO.

It is a public facing SaaS API which does not have much traffic in terms of requests, but would be catastrophic to be blackholed. So its that bad?

Regarding hardware failures- have never experienced any so far, but guess it's just a question of when then.

We now use a DigitalOceans managed database with 0 standby nodes, coupled with another instance running Django. It is working good.

We are however actually thinking about switching to a new dedicated server at another provider (Hetzner) where we are looking at having the Web server and the DB on the same server, however the new server will have hugely improved performance (which is sometimes needed), still at a reduced cost compared to the DigitalOcean setup.

The thing we are doubting is if having a managed db is worth it. The sell in is that everything is of course managed. But what does this mean in reality? Updating packages is easy, backups as well (to some extent), and we still do not use any standby nodes and doubt we will need any replication. So far we have never had the need to recover anything (about 5 years). Before we got the managed db we had it in the same machine (as we are now looking at going back to) and never had any issues.

Any input?

Yeah good question, maybe it feels overkill. I also found Gridsome which also looks very interesting

Thanks, had a look at Gridsome which is the vue equivalent- looks great

I tend to get jealous when I see people working with their hands, prefferably outside. Sometimes I even observe the guys cleaning the street and thinks, maybe its not that bad after all?

The times I have done such work (like construction) resulted in a much greater satisfaction and feeling in my body than after a day in front of the screen (even though I have been productive). Doing lots of running and gym but it does not generate the same feeling.

Have lately started to do something about it, maybe switch career totally.