<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>design pattern on </title>
    <link>/tags/design-pattern/</link>
    <description>Recent content in design pattern on </description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sat, 16 Dec 2017 09:06:31 +0000</lastBuildDate><atom:link href="/tags/design-pattern/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Golang flyweight pattern</title>
      <link>/golang-flyweight-pattern/</link>
      <pubDate>Sat, 16 Dec 2017 09:06:31 +0000</pubDate>
      
      <guid>/golang-flyweight-pattern/</guid>
      <description>The flyweight pattern is a design pattern I am not seeing that often in code bases but can be a good design pattern to reduce memory. The core idea is to initialize objects an share them as often as possible for reuse. Mostly the flyweight pattern can be seen in desktop UI implementation (GUI). In Java Swing, for instance, the JTable rendering uses this pattern, to reduce the computation needed for painting.</description>
    </item>
    
    <item>
      <title>Golang singleton pattern</title>
      <link>/golang-singleton-pattern/</link>
      <pubDate>Sun, 15 Oct 2017 17:47:18 +0000</pubDate>
      
      <guid>/golang-singleton-pattern/</guid>
      <description>There are a number of design patterns I am using on daily bases, and one of them is the Singleton pattern. In Golang penalties in performance are not so harsh as in other languages, if the application is not designed and written to perform with minimal CPU and memory footprint. I’m trying to keep my implementations as performing as possible, but sometimes explicit benchmarks can revile the details.
The singleton pattern is widely used in Object Oriented languages, and it is well worth to use it in golang.</description>
    </item>
    
  </channel>
</rss>
