<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>api on karlgrz</title>
    <link>https://karlgrz.com/tags/api/</link>
    <description>Recent content in api on karlgrz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Sep 2013 17:53:00 +0000</lastBuildDate><atom:link href="https://karlgrz.com/tags/api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stub Remote API Calls Locally with Nginx</title>
      <link>https://karlgrz.com/stub-remote-api-calls-locally-with-nginx/</link>
      <pubDate>Wed, 18 Sep 2013 17:53:00 +0000</pubDate>
      
      <guid>https://karlgrz.com/stub-remote-api-calls-locally-with-nginx/</guid>
      <description>One of the things that makes distributed systems development somewhat of a challenge is interacting with all the remote APIs that your system requires to function properly.
I find this a challenge when developing on the train (as I spend over 2 hours a day on one). 4G LTE is great and all, but there are dead zones and dropouts that make some API calls annoyingly long to respond.
Lately I&amp;rsquo;ve been messing around with stubbing out the remote calls locally using nginx, so I thought I would share how I do it.</description>
    </item>
    
  </channel>
</rss>
