Complexity: Deno or Postgres or DigitalOcean or Me?
I am trying to get my (new-to-me) Deno web server talking to a Digital Ocean managed database instance running postgres using remote access.
I just can't get there from here. I'm new to Deno, and tried both of the postgres modules I can find (postgres & postgresjs). I have a pretty standard DO droplet and a DO managed Postgres(ql) instance. I am trying to switch from using KOA - my favorite nodejs webserver which works - to Deno. I used the same string I use with psql to access the database when using Deno. It works with nodejs (the pg module) & psql. With both modules on Deno it fails with an invalid TLS blah, blah, blah.
The question:
So why am I posting this on HN? Because for the first time, I think I am going to abandon a new technology because the world is just too complex. I am unhappy about this, but it has made me think about how very, very many pieces need to work together. Is Deno good? Yes, (despite the TypeScript). I would like to adopt it. Is Postgres good? No, it is great! Is DO good? No, it is great (for me).
I adopt new technology all the time, within reason. Nginx, Docker, React Hooks, Threejs. Yup.
As a sole developer I take a pass on some things. Kubenetes - way to high a barrier for one person. TypeScript - it solves a problem for that in most cases I can avoid with `function foo({duckstring, frognumber})`. AWS - I can't afford a surprise bill for $10k. But none of these reasons or ones like them apply to Deno. It is clear to me why I don't go down these roads. The cost-benefit analysis is wrong for one person. But turning away from Deno is not this case.
So what is going on here? There is a possibility DO is the problem. Or Postgres is the problem. Or (gasp) even that I am the problem.
But when you think of how much Nodejs is out there and how many other pieces it connects to, maybe the lesson is that you can't replace. Maybe it explains why some technologies haunt us years/decade after it is clear they are inferior?
Just thinking.