this post was submitted on 19 Oct 2024
39 points (84.2% liked)

Programming

17661 readers
237 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
39
You're overcomplicating production (paravoce.bearblog.dev)
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/programming
16 comments fedilink hide all child comments
 

Sharing some lessons I learned from 10 years/millions of users in production. I’ll be in the comments if anyone has any questions!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 2 months ago* (last edited 2 months ago) (1 children)

I’m concerned that your preferred solutions may ignore the needs of working with peers. When I’ve worked with similar solutions before, we had a lot of on call, and it all went to the same person, regardless of who actually answered the phone.

Totally hear you and have the same experience myself. The approach I'm advocating for is simply running a binary on a server with rsync to deploy, and architecting your product around that limitation. Teaching a team the basics of Linux sysadmin will be incredibly useful for their careers, and it's something that the whole team can easily learn. Then you don't need to hire a k8s team -- any engineer can do some basic debugging when things go sideways.

[–] MajorHavoc 7 points 2 months ago

The approach I'm advocating for is simply running a binary on a server with rsync to deploy, and architecting your product around that limitation.

Intriguing!

I'm looking forward to your blog series on this.