home.social

#pongo — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pongo, aggregated by home.social.

  1. Btw. It's the 101st closed Pull Request in #Pongo. Chef kiss 👌😎

  2. See what I just merged! 🎉🐶 There are a few steps left, but hey! The First working version of #SQLite support in #Pongo landed in the main branch!

    github.com/event-driven-io/Pon

  3. #Pongo just reached 1300 🌟 on GitHub! Nice!

    If you’d like to match #MongoDB accessibility with #PostgreSQL powers - try it!

    github.com/event-driven-io/Pon

  4. Me ATM fighting with the #TypeScript generics while reshaping ⁠#Pongo API 😅

  5. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  6. Folks, it's happening! I started to work on #SQLite support for #Pongo. Stay tuned, more to come soon! 🤟

    github.com/event-driven-io/Pon

  7. @rdnt it's great that you're saying that, as that's why I created #Pongo: github.com/event-driven-io/Pon

    Together with #Emmet PostgreSQL support it makes it already possible (at least if you're in Node.js space).

    See:
    - event-driven.io/en/emmett_proj
    - event-driven.io/en/projections

    And more about Pongo internals: event-driven.io/en/pongo_behin

  8. Wiecie, co wyjdzie po połączeniu #MongoDB i #PostgreSQL? #Pongo. Nie żartujemy - jest to biblioteka do Node.js, która umożliwia łączenie się z Postgresem tak, jakby było to Mongo. Niektórym może to ułatwić życie, a inni mogą spojrzeć po prostu z ciekawości.

    #programowanie

    event-driven.io/en/crud_with_p

  9. In my recent article the leitmotif is how to bootstrap CRUD applications with #Pongo.

    If you’re not considering using my tool, or Node.js in general, then I believe it could be useful for the second hidden plot.

    This practical example was a chance for me to discuss what’s actually CRUD for me. When it’s fine to use it, when not.

    I also touched on how it relates to CQRS.

    Yes, I believe that you can do CRUD and CQRS at the same time. How come? Read more 👇
    event-driven.io/en/crud_with_p

    2/2

  10. 🎉🙌 Just got the first sponsor for #Emmett and #Pongo. Thank you, Christopher Watford, that’s much appreciated!

    You can also become one, and get “help me, help you” synergy. Sponsor tiers also include extended support for users and other perks. Check more 🙂👇

    github.com/sponsors/event-driv

  11. I'm being quite frank about my desire to make working on #Emmett, #Pongo, and other community projects sustainable. I'd like to get enough money from direct work on those projects to fully focus on them and bring more value to you and your projects.

    I think that supporting #OpenSource is a win-win for both sides. If you're using or considering using Emmett or Pongo tools, it's also some sort of due diligence to reduce the bus factor and maintain them continuously.

    1/

  12. Next year, I'll try to speak more about #Emmett and #Pongo at conferences (both on what you can do with them and my lessons learned building them).

    Do you have any recommendations on nice JavaScript/TypeScript conferences? I'd like to dive more into the JS/TS community.

  13. I might never reach full compatibility, as the API can have numerous permutations that I didn't predict. I don't want to block anyone waiting for the new release with the fix. I think that SQL is a decent fallback.

    That's why I added a few options for using #SQL in the #Pongo API.

    Read more about them in my recent article 👇

    event-driven.io/en/sql_support

    What are your thoughts?

    4/4

  14. Users should get a learning ladder. That's why I optimise the API and tooling for the newbies.

    That's why, in #Pongo, I'm trying to join two accessibilities: muscle memory and the Node.js community by reusing the #MongoDB client API and #PostgreSQL operation easiness and familiarity. I think that enables me to ramp up quickly and deliver business value by deploying the first version of your software to production.

    2/

  15. I had a lot of fun showcasing and explaining #Pongo with @FranckPachot on the #YugabyteDB stream.

    We went together to discuss why #Pongo uses #PostgreSQL. Seeing live how that plays with #nodejs and #typescript

    We also saw some SQL and explained how JSONB storage works, among many other things.

    Check it out here: youtube.com/watch?v=p-6fpV_GDE

    Leave the feedback afterwards.

    Boosting is also appreciated!

  16. I think that I made a good progress on #Pongo shell improvements.

    Pongo is my #Nodejs project that allows the use of #PostgreSQL as a document database with # Mongo-compliant syntax.

    I think that having a shell gives a good experience, allowing you to just play with tools.

    Just try it with:
    npx @event-driven-io/pongo@latest shell

    Here's how it looks 👇

    Check Pongo more here: github.com/event-driven-io/Pon

  17. If you'd like to see what I'm brewing with #Pongo, so using PostgreSQL as a strongly-consistent Document Database in #nodejs and #typescript, check the video youtube.com/live/P4r19rv4vOg

    There were some bloopers during live coding, presentation gods weren't with me today, but I think it's still a decent mark of the #Pongo journey 😉

  18. I just noticed we're one person short of having 100 people on the #Emmett & #Pongo Discord server.

    Who wants to be the 100th? 😀

    Feel invited! discord.com/invite/VzvxR5Rb38

  19. Boom 💣💥 New #Pongo Release with a huge set of changes!

    1. New Pongo shell, you can now use REPL without installing Pongo in your project.

    2. Optimistic Concurrency handling, no need for Mongo-like retries.

    3. You can use custom SQL updates, filtering with useful SQL tagged template literals to cover what's missing in the API,

    4. You can now print your queries to the console to track what's happening

    5. Added sample using hashtag#CockroachDB and typed client.

    #Nodejs #Typescript
    1/

  20. As I'm working on adding observability #Emmett and #Pongo, I decided to return to this idea and show how tests can drive predictable observability!

    Check the latest #ArchitectureWeekly release to see my take: architecture-weekly.com/p/maki

    As always, feedback is more than welcome!

    4/4

    #OpenTelemetry #Observability #softwareengineering

  21. In case you missed it, #Pongo got a big release with a new feature set yesterday.

    I know that reading release notes may sound boring, so I did a more human-readable write-up, especially for you.

    event-driven.io/en/pongo_stron

    I covered why getting a strongly typed client with full typing and storage migrations is a big deal in both DevEx and Performance.

    p.s. Pongo is like a Mongo but uses Postgres to give you strong consistency and user-friendly API. Check it out

    #nodejs #TypeScript #Postgres

  22. New big 🐶 #Pongo release!

    💪 Strongly typed client.

    You can define your collections typed schema and benefit from Typescript. It'll automatically generate the collections with provided names and typing.

    🖥️ CLI tool

    Together with typed schema, enables running database migrations upfront. That helps to get a performance boost, as you can disable automated schema setup (which is good for the dev environment but not for the prod).

    See: github.com/event-driven-io/Pon

    #nodejs #TypeScript #JavasScript

  23. First days after vacation and new #Pongo release. I added support for regular (non-pooled) connections. That should enable using it (and #Emmett) with solutions like Cloudflare Hyperdrive and connection pools like PgBouncer.

    Small, but important step. See more in 👇

    github.com/event-driven-io/Pon

  24. It's been a week since the initial 🐶 #Pongo release, and I have a big set of updates!

    1. I managed to close the basic coverage of document manipulation methods. I added initial versions of what was initially missing: replaceOne, drop, rename, countDocuments, count, estimatedDocumentCount, findOneAndDelete, findOneAndReplace, findOneAndUpdate, etc.

    1/

  25. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  26. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for and . I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  27. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  28. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂