I think they're saying "boring" in that there were no surprising or unusual choices. Go. Test. Mock. Three Postgres Databases, mostly immutable, partitioned

I think they're saying "boring" in that there were no surprising or unusual choices. Go. Test. Mock. Three Postgres Databases, mostly immutable, partitioned by data patterns / access patterns. Crontabs and shell scripts for data loading. No microservices, no multiple repo's, no strange/innovative technology. Pre-computing a bunch of stuff. 250-line query-builder instead of using GraphQL. vis: "The Complicators Gloves" https://thedailywtf.com/articles/the_complicator_0x27_s_gloves https://thedailywtf.com/articles/the_complicator_0x27_s_glov... ... I can imagine co-workers (past and present) who would have tried to add more complexity. `grpc` is a bit fancy (compared to `curl *.json`), which he admits to, but is also fairly battle-tested / boring, and gets some extra benefit of schema + performance. Maybe swagger or something would have been more "boring", but also veers a little away from "the default golang stack".