ignaciochiazzo

3 ms·

1.
Lean GraphQL Resolvers with Rich Models in Ruby: A Clean Architecture Approach(ignaciochiazzo.medium.com)
1 points by ignaciochiazzo 2y ago|0 comments
2.
by ignaciochiazzo 3y ago
Hey, thanks. It should be easier to get started with Whatsapp Cloud API. I have been using the gem for a while and it's working for me.
3.
Show HN: Ruby WhatsApp SDK Gem(github.com)
6 points by ignaciochiazzo 3y ago|2 comments
4.
Performance: Six steps required when working on performance optimizations(ignaciochiazzo.medium.com)
3 points by ignaciochiazzo 4y ago|0 comments
5.
by ignaciochiazzo 4y ago
Hey, I'm the author of the post. Thanks for the feedback! I will update the article with some of the insights from here. I wrote the post when I was investigating cursor-based pagination, which I had to implement at Shopify. We decided
6.
by ignaciochiazzo 4y ago
Sometimes the data is so big, and performance is critical that you don't have any other option than not to use offset.
7.
by ignaciochiazzo 4y ago
I strongly suggest not doing this since the application will be implementing `offset` in that scenario. This is the same as having Page-based pagination but with a cursor that acts a filter/sorting blob.
8.
by ignaciochiazzo 4y ago
Hey! Nice! I do think clients shouldn't store the cursor. This technique is neat, I will add it as an option to the Article (I’m the author).
9.
by ignaciochiazzo 4y ago
Hey thanks for the feedback. I will update the article.
10.
by ignaciochiazzo 4y ago
Query Limit +1 and then check the presence of the last item (Limit +1 item). Never use `count`. They are usually slow, and you might need to add more filters in the future. I will add this to the article.