<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>channel on GoScrapy Blog</title><link>http://goscrapy.com.ar/tags/channel/</link><description>Recent content in channel on GoScrapy Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>jackgris2@gmail.com (Gabriel Pozo)</managingEditor><webMaster>jackgris2@gmail.com (Gabriel Pozo)</webMaster><lastBuildDate>Mon, 03 Apr 2023 18:58:13 -0300</lastBuildDate><atom:link href="http://goscrapy.com.ar/tags/channel/index.xml" rel="self" type="application/rss+xml"/><item><title>Graceful Shutdown</title><link>http://goscrapy.com.ar/post/graceful-shutdown/</link><pubDate>Mon, 03 Apr 2023 18:58:13 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/graceful-shutdown/</guid><description>How to implement a graceful shutdown in Go? You need to start thinking about these kinds of questions when creating a server that needs to maintain a state. For example, if you have a web server running in one AWS EC2 instance and you fix some security issues and want to update the server. If you don&amp;rsquo;t manage correctly maybe you can lose the data that never was saved in the database or can provoke some bad user experience on every update because lose all connections without any response to the requests because you don&amp;rsquo;t wait to finish sending the response.</description></item></channel></rss>