Gregory's Server|
88 comments
@forrestbrazeal wow, I see this and I really do think technically you are your own VP. You might need another reorg seeing this diagram. @forrestbrazeal Wonder what software you use and what the process is: do you draw them with pencil/pen and then scan them - like many other professionals or do you directly produce them in software? Just curious! Congratulations! @forrestbrazeal fantastic, thanks so much, laughed so hard at Marco services. Have you shared that on here yet? I couldn't find it.   @forrestbrazeal@hachyderm.io The real trick to dealing with cloud is trying to ignore as many services as you can, adding new ones only when without them the system wouldn't work. I'd say that increases the survival possibilities a lot.  @forrestbrazeal I don't think I've ever seen smart use of containers in any database I've worked on. I'm sure they work well for those that build around them.  @jhooper @forrestbrazeal nah, that’s the thing, you need containers, otherwise all the stupid stuff would escape @forrestbrazeal I was just getting over the PTSD from experiencing this 'architecture' last year. The company had converted from Monolith to microservices.... to an insane degree. I was surprised they didn't have a "capitalize the tags" service. (well done on the graphic!) @forrestbrazeal you forgot the ”trying to keep up with weekly modulating best practices“ frontend layer. With regard to this, does anyone out there remember there was a great cartoon that was about one tiny little piece of unmaintained code in Linux maintained by some long gone developer that held up the entire stack? It might have been xkcd or something similar... Maybe this might draw a small synapse memory from someone. I'd love to find it! @forrestbrazeal I'm laughing so damn hard right now!! This is literally a picture of our architecture map!! 😂 😂 @forrestbrazeal This is great. Our team's Slack channel is having fun "relating" to this architecture diagram! @forrestbrazeal I lost it at the VPN of sadness, but it was the data swamp that really made me cry @AnokheeTara @forrestbrazeal that moment when management blames engineering for their Data Lake not working as seamlessly as the well-dressed salespeople said it would. @forrestbrazeal I guess it's part of the joke but:  @forrestbrazeal Uh oh. My circa 2022 architecture needs to evolve - it has far too much duct tape to be 2023 compliant. @forrestbrazeal a png that will find its way to cubicles everywhere very soon  @forrestbrazeal 😁 the one tiny cron job that keeps the Cloud Rube Goldberg machine from collapsing. @forrestbrazeal it would be funnier if it weren’t so trueeee. Just missing “serverless” @forrestbrazeal missing: that one crown job that is essential to the business that takes EVERYTHING down. @forrestbrazeal I've worked on more of these pieces than I'm comfortable admitting in public.   @forrestbrazeal how did you use one diagram to accurately depict every system I’ve ever worked on. @forrestbrazeal @RainofTerra the 4 boxes at the bottom personally hit hard. @RainofTerra @forrestbrazeal Strong same. It’s XKCD-2347 but it’s a cron job. @forrestbrazeal Is "blame radius" meaning "stuff in here, someone is to blame for", or does it mean "this is RADIUS' fault"? Because the latter makes me excited to have a new way to do containers wrong, but I feel like it's supposed to be the former? @forrestbrazeal Is that splotch in the Data Swamp a goose that Ian Coldwater left behind when escaping? @forrestbrazeal Though, I say, where is: missing network documentation or network documentation never or haven't been updated in years. 😂  @forrestbrazeal @streamofron you know, that one tiny cron job has saved my ass several times. @forrestbrazeal I'm sad to say I've been the engineer giving the cute business propaganda version of this presentation at a company I used to work for. I'm not proud of that phase of my life. @forrestbrazeal Yep there's always one of those. @forrestbrazeal it forgot, that the cron job holding everything up, is actually undocumented... @forrestbrazeal This is giving me a chuckle and a tear because it's so accurate to live architectures I've seen before 🥲 That's just awesome <3 Though there probably should have been a tiny sad IAM locked in a cell whining "please can I be your friend?" @forrestbrazeal @forrestbrazeal welcome to 2019 - this is a great idea, 2020 - it’s just tricky cos of Covid, 2021 - oh, people actually want to use this, 2022 - MAKE IT WORK, 2023 - what if we use a different cloud service?, 2024 - and repeat……..😫 @forrestbrazeal thanks for reminding me why I don't do anything like backend / full stack anymore 😆 |
@forrestbrazeal this is too good!