Polyglott

Deployment, scaling, monitoring, service discovery, configuration, we may or not be aware of such problems when we start but we definitely have to find a solution for them if we want to have a sustainable infrastructure for implementing software which is able to support increasing levels of success. There are many approaches to tackle the aforementioned situation, and a good first step is to standardize the application representation from the infrastructure point of view. [Read More]

Abstractions We use abstraction to be able to cope with the high amount of information our senses receive all the time, by filtering and focus on what we really need, without that ability we would not be able to function properly in life. When we talk about applications, it is useful to abstract them as packages. There are some things we would like to do with those packages, which are finally going to be delivered to a client or user. [Read More]

Continuous delivery is a hot topic these days, mostly because of the DevOps movement which aims to improve collaboration among different people involved in the process of software delivery, by embracing automation and constant communication.

[Read More]

On my quest of learning I heard about this relatively new language called go. I don’t remember well the details of why I had the desire of learning it, but as I normally do in order to learn a new language or tool, I write code to test the features and get an overview of what I can accomplish using it and… I also read the first chapters of this book: Programing in go

[Read More]

In this post I’m going to use Terraform to define and launch a DigitalOcean server and a DNS DigitalOcean A Record.

[Read More]

I few months ago I wrote a little module for mocking Waterline models, you can check my related post here “Weaselpecker: Node.js- Waterline Simple Mocking Library”. It seems the module was useful for some developers (which is great 😀 ) so I took a few hours to review my code and add a couple extra features. I’ve released v1.1.0 which is available on NPM https://www.npmjs.com/package/weaselpecker. Installation npm install weaselpecker --save-dev Examples here https://github. [Read More]

RequireJS is a module loader for JavaScript. RequiresJS is based on the AMD (Asyncronous Module Definition) API specification, which provides a mechanism for defining and consuming modules. When you require or use a module, it will be retrieved asynchronously and cached at the time you need it, that improves performance since you don’t need to load all your dependencies (JavaScript files) at the same time.

[Read More]

Modeshape

Modeshape is an hierarchical data store written in Java and is part of the JBoss portfolio . ModeShape clients are based on JSR 283 also known as JCR (Java Content Repository). There’s another popular implementation of JCR called Jackrabbit, part of the Apache Software Foundation.

Content Repositories such ModeShape are great for data organized in a tree like structure such Content Management Systems, Digital Assets Managers, Document Management Systems, Social Collaboration Systems etc.

[Read More]

Code coverage is a measure of how much of your code has been  tested. Code coverage tools run a set of metrics in order to determine if your code has been completely tested, reducing the chance of  unwanted bugs.

You have to take into account that even if your code has 100% code coverage, that doesn’t guarantee all your tests are correct, there are some logical bugs you might miss, but as with anything, practice will help you with that.

[Read More]

In this post I’m going to list the steps for setting up a Node.js project with unit testing.

[Read More]