* Is boring tech good because older tech with lots of commits is more likely to have identified bugs?
* Is boring tech good because it is easier to find devs with skills in those areas?
* Is boring tech good because it has lots of fleshed out examples to follow/SO support/packages?
* Is boring tech good because it is simpler and has less moving parts?
Simply saying "Postgres" or "JVM" doesn't imply boring either. Both of these have lots of advanced features and complexity. Your interactions need to be boring (simple, avoiding advanced features). Moreover it's very powerful to make your application boring. What if your whole app could only read/write data in one place? What if your whole app could be single threaded rather than multi-threaded (and still deliver results)? There are good reasons not to do these things, but those cases are rarer than the times we jump to these solutions which can create difficult problems that make our lives harder later