<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nosql on Manuel Bernhardt</title><link>https://manuel.bernhardt.io/tags/nosql/</link><description>Recent content in Nosql on Manuel Bernhardt</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Feb 2023 20:54:16 +0100</lastBuildDate><atom:link href="https://manuel.bernhardt.io/tags/nosql/index.xml" rel="self" type="application/rss+xml"/><item><title>The case for document-oriented databases</title><link>https://manuel.bernhardt.io/2013/07/28/the-case-for-document-oriented-databases/</link><pubDate>Sun, 28 Jul 2013 14:21:41 +0200</pubDate><guid>https://manuel.bernhardt.io/2013/07/28/the-case-for-document-oriented-databases/</guid><description>&lt;p&gt;Last week, I started working with &lt;a href="http://angularjs.org"&gt;AngularJS&lt;/a&gt; for a real-world project - I had played with Angular before, mainly to see how it differs from &lt;a href="http://knockoutjs.com"&gt;KnockoutJS&lt;/a&gt; which I had been using intensively before. This post is not about AngularJS itself (I may write one later on when I have a better perspective about the framework), I&amp;rsquo;ll just say that my first impressions about it are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;it lacks good documentation - the existing documentation doesn&amp;rsquo;t exactly have the right &amp;ldquo;feel&amp;rdquo;, and is incomplete&lt;/li&gt;
&lt;li&gt;when coming from Knockout, Angular feels rather invasive, given that it is a &amp;ldquo;full-blown&amp;rdquo; framework rather than &amp;ldquo;just&amp;rdquo; a MVVM mapping tool&lt;/li&gt;
&lt;li&gt;my current impression is that the learning curve looks like a roller-coaster - there&amp;rsquo;s moments of intense productivity interrupted with high amounts of &amp;ldquo;not getting anywhere, why on earth am I using this sh*t&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That being said, there&amp;rsquo;s one thing that AngularJS seems to get really right: it makes it possible to map documents to the UI without imposing its own design philosophy on the said document. With KnockoutJS for example, you&amp;rsquo;d have to make sure certain fields were provided as arrays, and generally had to know really well how the different bindings worked before knowing into what shape to bring your data so that the UI would do what you wanted.&lt;/p&gt;</description></item><item><title>MongoDB-based Cache for Play 1.2.x and Play-Scala</title><link>https://manuel.bernhardt.io/2011/11/18/mongodb-based-cache-for-play-1-2-x-and-play-scala/</link><pubDate>Fri, 18 Nov 2011 22:33:57 +0100</pubDate><guid>https://manuel.bernhardt.io/2011/11/18/mongodb-based-cache-for-play-1-2-x-and-play-scala/</guid><description>&lt;p&gt;In case anyone needs this: &lt;a href="https://gist.github.com/1377952"&gt;https://gist.github.com/1377952&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;ve got to bootstrap it in some bootstrap job like so:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt"&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-scala" data-lang="scala"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nc"&gt;ScalaCacheAccessor&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;set&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;MongoCacheImpl&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;It&amp;rsquo;s only tested with the Press module so far (shared state is evil anyway 😉 )&lt;/p&gt;</description></item></channel></rss>