<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Poc on The Mole&#39;s OpenNMS (TM) Dev Diary</title>
    <link>/tags/poc/</link>
    <description>Recent content in Poc on The Mole&#39;s OpenNMS (TM) Dev Diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Jan 2019 14:00:00 +0100</lastBuildDate>
    
	<atom:link href="/tags/poc/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Graph Service - Proof of Concept</title>
      <link>/posts/graph-service/1-poc/</link>
      <pubDate>Sun, 20 Jan 2019 14:00:00 +0100</pubDate>
      
      <guid>/posts/graph-service/1-poc/</guid>
      <description>The Topology Map in OpenNMS has some architectural problems. Mainly that there is no &#34;service layer&#34; implemented, which causes mostly performance issues. Besides this no API or persistence model is enforced. This prevents easy integration with 3rd party applications or even provide a new UI implementation.
 Therefore I started playing around with a new Topology implementation (See issue HZN-1452) for more details). In order to not confuse it with existing implementations, it is called Graph Service or Graph Engine here.</description>
    </item>
    
  </channel>
</rss>