regexer
Forrest Brazealgood morning and welcome to 2023
If you enjoyed this comic, you can find lots more at https://goodtechthings.com!
snswamy@forrestbrazeal
Excellent!
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!
@snswamy These are done in Procreate on an iPad Pro with an Apple Pencil.
ralf warümme tauscher@forrestbrazeal thanks. can't stop reading it ;)
:David Campey@forrestbrazeal fantastic, thanks so much, laughed so hard at Marco services.
Have you shared that on here yet? I couldn't find it.
Jeroen Postma 🇪🇺@forrestbrazeal oh thanks, love it! ❤️
Will C 
@forrestbrazeal wow, I see this and I really do think technically you are your own VP. You might need another reorg seeing this diagram.
urig@forrestbrazeal OMG this is brilliant
ǝʌɐp@forrestbrazeal "this is what peak performance looks like"
jonossa seuraava
Aaron Ogle@jonossaseuraava @forrestbrazeal 😂 that’s a good one too
Dan McDonaldAre you missing naming services hacks?
knightly. @forrestbrazeal
This is entirely too accurate.
This is entirely too accurate.
Ignas Kiela@forrestbrazeal 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.
rick@forrestbrazeal me every second day: "Maybe i should do sth with wood?"
Thomas Schalldach@forrestbrazeal this is brilliantly designed and true
Jhooper@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.
Tim Kellogg@jhooper @forrestbrazeal nah, that’s the thing, you need containers, otherwise all the stupid stuff would escape
Daniel Smith@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!)
srsh@forrestbrazeal you forgot the ”trying to keep up with weekly modulating best practices“ frontend layer.
Futurist Jim Carroll
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!
NightDweller
robotbill@forrestbrazeal I loled at “Résumé”.
Terrafied Kestrel 
@forrestbrazeal I'm laughing so damn hard right now!!
This is literally a picture of our architecture map!! 😂 😂
James Holden@terrafiedkestrel @forrestbrazeal ours too! It’s scarily accurate.
Stone Bear 
@forrestbrazeal Real talk. Only its three or four tiny cron jobs...
Curtis Bray@forrestbrazeal This is great. Our team's Slack channel is having fun "relating" to this architecture diagram!
Irkam@forrestbrazeal I guess it's part of the joke but:
1. Where are the clients?
2. This lacks a legacy in-house critical service that hasn't been updated in decades and does the actual job.
1. Where are the clients?
2. This lacks a legacy in-house critical service that hasn't been updated in decades and does the actual job.
keith@forrestbrazeal Uh oh. My circa 2022 architecture needs to evolve - it has far too much duct tape to be 2023 compliant.
Cranky David@forrestbrazeal
LOL "VPN of sadness"
LOL "VPN of sadness"
Nican
mike bayer 
@forrestbrazeal a png that will find its way to cubicles everywhere very soon
Omelette norvégienne@forrestbrazeal excuse me, this is privileged information
Phil Stevens 
@forrestbrazeal I feel seen.
@forrestbrazeal this uncannily describes the stack at $dayjob
Justinmwhitaker@forrestbrazeal 😁 the one tiny cron job that keeps the Cloud Rube Goldberg machine from collapsing.
Dmitri Kalintsev@forrestbrazeal no lies detected! :)
Chris Patten@forrestbrazeal it would be funnier if it weren’t so trueeee. Just missing “serverless”
Dan Ciruli@forrestbrazeal I've worked on more of these pieces than I'm comfortable admitting in public.
Bram Diederik aka daft_dutch@forrestbrazeal where is the rc.local hack to get everything started at boot?
Berkubernetus@forrestbrazeal OUCH! Way too accurate.
Terra Field@forrestbrazeal how did you use one diagram to accurately depict every system I’ve ever worked on.
PierreNick 
💾@forrestbrazeal @RainofTerra the 4 boxes at the bottom personally hit hard.
@pierrenick @forrestbrazeal that cron job box brutalized me
@RainofTerra @forrestbrazeal Strong same. It’s XKCD-2347 but it’s a cron job.
Renoir Boulanger
fraggLe!@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?
@fwaggle the former, it’s a takeoff on “blast radius”
Arnan de Gans@forrestbrazeal pretty much yes...
BillStewart415@forrestbrazeal Is that splotch in the Data Swamp a goose that Ian Coldwater left behind when escaping?
Ithanul@forrestbrazeal
I think I laugh a bit too much at this. Especially at: one tiny cron job keeping everything from falling apart.
Though, I say, where is: missing network documentation or network documentation never or haven't been updated in years. 😂
Bryan Entzminger@ithanul @forrestbrazeal I’m sorry… what is documentation?
Dani (She/They)@forrestbrazeal “Services that like to watch” got me.
Bob Morris@forrestbrazeal "One tiny chron job"!
zen@forrestbrazeal event bus -> resume hurt my feelings lmao
Dulany-100B-v0.2-GPTQ