You're going to have outages in production. They're inevitable. The question is how to best minimize outages, both their frequency and duration. Common wi...

cross-posted from: https://lemmy.world/post/21023181

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

I hope this series will be useful to the self-hosted and small web crowds—tips for tools to pick and the basics of server management.

  • something_random_tho@lemmy.worldOPEnglish
    153·
    2 months ago

    Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I’ve never written a blog before (or much of anything!), and I’m sorry you didn’t find value in this.

    I wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.

    I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.

    • just_another_person@lemmy.worldEnglish
      142·
      2 months ago

      Well, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:

      • Try starting with a simple topic flow: topic -> synopsis/purpose of why you’re writing -> background -> observations -> point<>counterpoint loop to elaborate on purpose -> closing
      • Stay away from asserting your point in the title unless you’re showing definitive proof of something
      • Find ways to speak to who may find your writing useful towards the beginning. “If you have a similar problem like X…”, “People who use X may find…”, or “Anyone having similar X experience may find…”. Something like that.