<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>docker on </title>
    <link>/tags/docker/</link>
    <description>Recent content in docker on </description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 27 Apr 2018 19:23:31 +0000</lastBuildDate><atom:link href="/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Undertow REST API</title>
      <link>/undertow-rest-api/</link>
      <pubDate>Fri, 27 Apr 2018 19:23:31 +0000</pubDate>
      
      <guid>/undertow-rest-api/</guid>
      <description>Part of my daily routine is to consume, design and deliver services built for HTTP clients. This might manifest in something special like WebSocket, Protobuf but most often a plain JSON REST API. In any case, the performance is key, and an Undertow REST API with JAX-RS can deliver a stable performance under consistent load.
In this article, I will cover some basics for setting up and deploying a REST API with Undertow, in Docker.</description>
    </item>
    
    <item>
      <title>Web Services in Docker with Golang</title>
      <link>/web-services-in-docker-with-golang/</link>
      <pubDate>Tue, 18 Jul 2017 20:26:55 +0000</pubDate>
      
      <guid>/web-services-in-docker-with-golang/</guid>
      <description>This post is a walkthrough on my approach to develop and deploy Golang web service in Docker container. There are many reasons for integrating Docker into the daily routine as a developer, one being the simplification of setting up a separated runtime environment. Using containers in production has, even more, advantages from simplified release to better performance. Kubernetes and Docker Swarm is gaining more and more space, which I think is partly because of the simplified management on IBM Cloud and Google Cloud Platform.</description>
    </item>
    
  </channel>
</rss>
