<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postmortem on</title><link>https://codeinfocus.com/categories/postmortem/</link><description>Recent content in Postmortem on</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Apr 2021 09:24:02 +0300</lastBuildDate><atom:link href="https://codeinfocus.com/categories/postmortem/index.xml" rel="self" type="application/rss+xml"/><item><title>The tale of misbehaving Node.js microservice - Postmortem</title><link>https://codeinfocus.com/blog/2021-04/the-tale-of-misbehaving-node.js-microservice-postmortem/</link><pubDate>Wed, 07 Apr 2021 09:24:02 +0300</pubDate><guid>https://codeinfocus.com/blog/2021-04/the-tale-of-misbehaving-node.js-microservice-postmortem/</guid><description>&lt;p>&lt;em>&amp;ldquo;You don’t build production shit on your machine!&amp;rdquo; - &lt;a href="https://pushbuildtestdeploy.com/">Yuval Oren&lt;/a>&lt;/em>&lt;/p>
&lt;h2 id="the-problem">The problem&lt;/h2>
&lt;p>About a month ago we started getting weird issues with one of our Node.js services in change of extracting data from the database to our analytics platform. After a while, we discovered it did extract only partial data, producing no errors.&lt;br>
We spent long hours trying to catch the problem, which was difficult since we couldn’t recreate it neither on development machines, nor on our test clusters.&lt;br>
Furthermore, the issue would go away for a while after some tweaks and mysteriously come back after a while.&lt;/p></description></item></channel></rss>