Guide: How to use Meteor with Postgres 😮

Hi Satya would be interesting to learn more about why you think this technology is irrelevant. I think you are partially right, and the parts you might be right about might have been irrelevant for many for a very long time.

I haven’t used Publications for at least 8 years. I adopted React from its first releases and found Redux to work best with what I need to do.
I don’t use Cordova or Meteor Desktop, and I am pretty fine with React Native or PWA (being a React dev. anyway).
Now my AI tools are pretty fine with understanding my Meteor specifics, and it helps me a lot.
I started a couple of DB-less websites in React to have them hosted with Netlify, and I found myself doing them in Meteor too :)) … because it is fun and joy.

If I could get CDN cached dynamic components, I would be the happiest developer (in my house).
I also need to get into passing Methods (DB queries) through Redis, I found the solution, and I just need to allocate some time for wiring things right. This is similar to redis-oplog but for methods.

I recently tried NextJS (again). I just can’t stand the fetching syntax and concept and I hate the way images are being imported and some other parts that had to be made a NextJS React component. I am also not a big supporter of SSR because I consider that the cost of tech should be shared between the provider and consumer - I’ll give you some JS … you HTML it yourself. Of course this works ok up to a certain bundle size but works better for apps with recurrent visits such as SaaS or social networks etc. SSR is great for the first visit but I couldn’t find another use for it in what I do. I host my own Prerender so I will only pay $5 a month to have all the buggers out there crawl my pages.

3 Likes

I’m correcting my own statement of earlier: the deadlocks were not caused by FerretDB not supporting sparse indexes. FerretDB 2.2 does support sparse & unique indexes—great! The deadlocks were causes by the accounts-base and accounts-password packages concurrently creating such indexes, which is handled well by MongoDB, but not well by FerretDB/Postgres. I updated my package to fix only what is essential to avoid this error, by simply making createIndexAsync sequential (using a promoise chain).

1 Like