I’ve been discussing the “schemaless” view of NoSQL with some fellow developers and have been tweeting a bit about it and yesterday I started to read a new book: “NoSQL Distilled – A brief guide to the emerging world of polygot persistence, Pramod J.Sadalage & Martin Fowler (2013)” (Sadalage & Fowler 2013). So far I really appreciate it and I’ve extracted two sentences from the book that I think is really informative and clear when it comes to schemas and NoSQL:
“… whenever we write a program that accesses data, that program almost always relies on some form of implicit schema” – (Sadalage & Fowler 2013)
“Essentially, a schemaless database shifts the schema into the application code that accesses it.” – (Sadalage & Fowler 2013)
This will show you how easy it is to get CouchDb up and running on a Windows machine. I will show you how to use the builtin admin tool to secure the server as well as the database that we will create. I will then show you how easy it is to interact with it using a C# client called, MyCouch.
This is going to be a really super simple sample showing you how to set up a single page application (SPA) using PathJs, KnockoutJs and HeadJs.
Just got a new NuGet out – “MyCouch – a Simple async CouchDb client for .Net” – which uses the async HTTP-client to interact with the HTTP API of CouchDb. It tries to mimic the domain-language and structure of CouchDb and lets you work with pure JSON or using entities/POCOs. The future will bring builtin support for caching, proxies/sharding, etc. Go grab it now and try it out. It’s on NuGet. Documentation is improved continuously.
The goal of this post is to give you some insight in how easy it is to get stuff done with Node.js (Node). It’s not going to be an incredible business application but it can still give business value. We will make use of Node and Handlebars to create a simple and custom report from issues stored in the public YouTrack repository for ReSharper.
What is old today can be part of history. What is new today will be outdated tomorrow. What is outdated tomorrow will not be part of history
Evolution shouldn’t be synonym to forgetting the past. The world is evolving very rapidly and of course the era of now will be the history of the days to come. But is today’s era anything exceptional? Or is it just something being passed by on the course to a more futuristic world? I hope not! I hope we take a pause and look back. Don’t demolish what has been. Let it be part of the future so that we don’t forget. Build new houses but be careful. History can’t be restored. History can’t be rebuilt. History can either be remembered or forgotten.
Quite easy, just head over to NodeJs.Org and download and install it. The next step is to install Express. Fire up Git-bash or a command prompt and use the Node package manager (npm) to install Express globally:
npm install -g express
When I started to consume Fleck it just lacked some of the features (which is also what I like about Fleck, it’s simple and bare bone and easy to get started with) I wanted and I also wasn’t sure I would go with Fleck, so I created a small layer sitting on top of Fleck.