@masukomi
I don't use #mongo regularly, just #jsonb in #pg, so I'm guessing:
1. Mongo users could port data into pg using existing #backup & #recovery infrastructure, then they'd have both SQL and mongo query/dump/load options for future #migrations
2. The pg API will lag mongo's and sunset existing features later. And #SQL api as a fallback
3. A mongo app could transition to pg incrementally or partially, increasing maintainability by using mongo queries and SQL queries where they make sense

Are you in #PostgreSQL world, bashing your head against the #JSON (or #JSONB) column?

Check out the new #cheatsheet!

https://aiven.io/developer/postgresql-jsonb-cheatsheet

Can I use a #relationaldatabase to store, parse and analyse #semistructured #JSON data?

It turns out #PostgreSQL is pretty good at it with the dedicated #jsonb functions

Check out an example, finding a good restaurant in India!

https://aiven.io/blog/pg-json-indian-restaurants

Typical example where YAGNI failed me. I wrote a java lib for accessing a specific rest API. Because Y., I had only two #maven modules: api and jaxrs-jackson-impl.
Now another project used #jakarta #jsonb. Sigh.

Blog post:
How to use #jjwt (by @lhazlewood@twitter.com) with #Jakarta #jsonb (Bind-API). Works with both Eclipse Yasson (used by @OpenLibertyIO@twitter.com) and Apache Johnzon.

https://blog.bmarwell.de/2022/05/12/using-jjwt-with-jakarta-jsonb.html