<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>fiber on GoScrapy Blog</title><link>http://goscrapy.com.ar/tags/fiber/</link><description>Recent content in fiber on GoScrapy Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>jackgris2@gmail.com (Gabriel Pozo)</managingEditor><webMaster>jackgris2@gmail.com (Gabriel Pozo)</webMaster><lastBuildDate>Fri, 30 Jun 2023 19:15:51 -0300</lastBuildDate><atom:link href="http://goscrapy.com.ar/tags/fiber/index.xml" rel="self" type="application/rss+xml"/><item><title>Different approaches to do Pagination in an API Rest</title><link>http://goscrapy.com.ar/post/different-approaches-to-do-pagination-in-an-api-rest/</link><pubDate>Fri, 30 Jun 2023 19:15:51 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/different-approaches-to-do-pagination-in-an-api-rest/</guid><description>Introduction In this post, I will talk about Pagination in Rest API, my idea was only to talk about that topic and create a tiny repository where I can show a simple example. But I started adding some features, like Docker, Kubernetes, Makefile, etc. (sometimes that kind of thing happens 😀) That made me think that I can explain many topics with the same repository, the idea will be to add more features or technologies and every post will be related to un tag version.</description></item><item><title>How to Write a Pub Sub Service With Go</title><link>http://goscrapy.com.ar/post/how-to-write-a-pub-sub-service-with-go/</link><pubDate>Sun, 04 Jun 2023 12:14:36 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/how-to-write-a-pub-sub-service-with-go/</guid><description>An overview of the Pub/Sub pattern and how it works. What is Pub/Sub? The Pub/Sub (publish/subscribe) pattern is a messaging pattern used in distributed systems to enable asynchronous communication between components or systems. It allows for the decoupling of senders (publishers) and receivers (subscribers) by introducing an intermediary called a message broker or message bus.
How does its work? Publishers: Publishers are responsible for sending messages to specific topics. A topic is a named channel or category to which messages can be published.</description></item></channel></rss>