Miscellaneous

[pedr0limpio]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[pedr0limpio]

Greetings! I believe we don't need to open issues like #9 , #10 , #11 , #12 . I understand that issues #2, #3, #4 and #5 already include integration with the database, because how can I "say" that function "x" is ready if I haven't tested it with persistence?

If the feature is separated from persistence at the pull request level, there is a high chance of rework. What do you think?

@lpglinard @silrenan @Cintyabio

[Cintyabio]

I agree 😁

I think we don't need extra issues like #9, #10, #11, and #12 because the integration between frontend, backend, and database is all connected. Testing them separately could lead to extra work later if something breaks during integration. Instead, it's better to handle the entire flow, frontend to database, within the existing issues (#2, #3, #4, and #5). This way, everything is tested together, avoiding rework.

What do you think @silrenan ?

[silrenan]

Hello there,

I see what you guys mean and I can concur with it, @pedr0limpio, I will go ahead and rearrange the issues mentioned by @Cintyabio and merge them on theirs earliest numbered mentions.

[silrenan]

OK, issues merged together on their respective earliest numbered twin. Later I will tinker their descriptions better.

[silrenan]

@pedr0limpio, @Cintyabio, maybe we move this to another discussion outside Welcome discussion to continue tracking this issue? #31

[pedr0limpio]

@silrenan @Cintyabio and @lpglinard - Take it or drop it:

Choose your destiny:

https://dzr.page.link/bGyo7efhLcN9Mn7HA
https://www.hipsters.tech/tech-guide-graphql-no-ecossistema-mobile-hipsters-ponto-tech-447/
https://open.spotify.com/episode/6hU06sHtora4xFuP2NeX3P?si=JSy1h1crR7CUoJjqDYEljg

[silrenan]

Let me take a step back here and translate to English. Since the podcast was listened on pt-br, I ended up originally writing my rating also on pt-br.

The podcast's comments on GraphQL, even for me who is not a dev, are superficial and fail to explore important points clearly. Comparisons between GraphQL and REST need to go beyond appearance and address issues such as data granularity, payload structure, access control, and performance in mobile environments.

The point about roundtrips is pertinent, but lacks context. GraphQL was created precisely to reduce the need for multiple API calls, aggregating data from different sources in a single query. However, this advantage depends on a well-designed schema. If poorly structured, the opposite effect can occur: multiple resolvers that generate several internal calls to the backend, which compromises performance.

Caching is a topic that deserves more attention. While REST benefits from native caching via HTTP, GraphQL presents challenges due to the dynamic nature of its queries. The explanation about queries and mutations is limited to the basics. In GraphQL, queries are used to retrieve data and can be cached, while mutations change data and should not be cached. However, this is just the beginning. They failed to include subscriptions, which are crucial for real-time use cases, such as notifications or data streams, an important difference compared to traditional REST.

In short, GraphQL is a powerful tool that, in order to bring concrete benefits, requires careful schema design, discipline in the use of queries and mutations, and extra attention to caching, performance, and security. A more technical and detailed analysis of its pros and cons would bring much more value to the discussion.

And finally, the positive point of the podcast is the cognitive dissonance caused by the "poor" comments that made me try to better understand what they were talking about.

What do you think @Cintyabio ?

[silrenan]

@Cintyabio I summon your reflections on the designated podcast transmission. Your insights—forged in thought—are integral to the architecture of our foundation as developers. In this crucible of calibration, your opinion becomes signal, not noise. Speak, and let the @pedr0limpio evolve us in the right direction.

[pedr0limpio]

As Beyonce would say...to the left, to the left