What’s everyone’s server naming scheme?

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    I think you choose a poor example.

    When I say long name I wasn’t implying meaningless ones.

    Sooo, that example wasn’t exactly “contrived” - it’s based on a standard I see where I work.

    DB - it's a database!
    DW - and a data warehouse at that!
    ORCL - It's an Oracle database!
    HHI - Application or team using / managing this database
    P - Production (T for Test - love the 1 char difference between names!)
    01 - There may be more than one.
    

    This is more what I’m arguing against - embedding meta-data about the thing into its name. Especially when all of that information is available in AWS metadata.

    [Site][service][Rack] makes sense for on-premise stuff - no argument there.

    I’m just saying long names dont have to be obtuse or confusing.

    Agree

    • EpicFailGuy@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      Not to butt in into your conversation, just wanted to drop that me and my colleagues use what we call the “clone cars” method to combat our company’s naming scheme

      So for example we dubbed CAPROD01 “Cappy” NASPROD01 became “Nasir” LTPDEV02 became “Luigi” (because he’s always number 2)

      Of course in written communication we use the full name (which is much less of an inconvenience) and we always double check in conversation or spell out full names before doing anything critical