Static Analysis Tooling for C# and .NET, NDepend in Depth

As a software architect I often have to analyze many applications code in order to perform a quality check.

Is the code looking good? What about its complexity and test coverage? Can I consider the code as maintainable with a good scalability?

Of course I won’t spend my whole time reading each source file, it would be too long and for sure useless. Hopefully a set of rules and tools can help if you are in this same situation.


Impact mapping: business success in software development

We had a chance to meet the author of Impact Mapping Gojko Adzic at OCTO Technology. After the interview and Product Owner Survival Camp workshop attendance in London, where Gojko explained us the advantages of this new method, we would like to share with you some ideas about it.

What is Impact Mapping?

Impact mapping is a visual strategic planning technique that helps teams to align their activities with overall business objectives and make a better decision.

Blog 1

Impact Mapping prevents organisations from getting lost while building products and delivering projects by clearly communicating assumptions.


SQLFire from the trenches

In a first article, I have explained why I think that NewSQL is a disruptive storage technology designed for traditional Information Systems. NewSQL relies on a scalable architecture and is designed to run on commodity hardware. In order to get actual figures for SQLFire, we have built a Proof of Concept for stress test purposes. The goal of this article is to give you some feedback on these stress tests in the chosen scenario.


The new Web application architectures and their impacts for enterprises – Part 2

In the first part of this article, we talked about new front-end architectures, which consist of JavaScript Web applications using APIs provided by a back-end server: The new Web application architectures and their impacts for enterprises – Part 1.

We saw that they recently emerged thanks to the increasing performance of browsers and the rise of industrialization tools for JavaScript development.

In this second part, we will focus on:
  • reasons why you should adopt these new architectures;
  • opportunities they provide;
  • impacts for enterprises.


The new Web application architectures and their impacts for enterprises – Part 1

Web applications evolve. From static HTML sites first to AJAX applications more recently, through multiple dynamic technologies (PHP, ASP, Java, Ruby on Rails…), Web application architectures and their dedicated tools regularly experience major advancements and breakthroughs.

For two years, we have seen a new wave of technologies coming, transforming the landscape of Web applications. Unlike RIA or AJAX before, there is no well defined name yet for this new trend. We will call it “MV* client-side architectures”.

Here is the main principle: the server no longer manages the whole page but only sends raw data to the client; all the pages generation and user interactions management is done on the client side, that is to say in the browser.

In this post, we will go into details of this architecture and explain why it is emerging. In a second post, we will see why it is relevant to embrace it today, opportunities they offer and what are the likely impacts for enterprises.


Let’s dig into SQLFire

A year ago, I promised in a previous (French) article to test the ability to migrate a standard Hibernate/SGBRD application to a NewSQL technology. It is now time to give you the results of our investigation. Don’t worry I will first sum up this previous article and explain why I strongly believe that NewSQL is an important subject. Then I will present the hypothesis of our POC. And finally I will give you the results of this POC, our conclusions about what we will do the same way and what we will do differently on a real project.

Edito March 2014

We are initiating a new set of articles in order to give you our opinion concerning what’s happening in the Tech world.

Octo hosted the first Swiss DevOps Meetup

DevOps CH Meetup Logo

Octo Technology hosted last week in Lausanne (Switzerland) the first meetup of the Swiss DevOps community.

As guest speaker, @NuttySwiss, Senior Site Reliability Engineer at Twitter gave a talk about Apache Mesos, Aurora and SRE.
Mesos is the heart of Twitter infrastructure and allows to run multiple services in a reliable way inside their data centers.
Aurora is the scheduler that run on top of Mesos.
SRE stands for Site Reliability Engineering.

Octo was happy to welcome this meetup and is looking forward to help the Swiss DevOps community to grow.
For further details about the meetup:

Docker container’s configuration

As we saw in the previous post, Docker basic usage seems pretty simple. Let’s try to dig a little deeper into the configuration management.

From an OPS perspective, we can consider containers as application black boxes, without caring about how they are built, and simply use them. However there are several aspects of a container that must be configured to ensure their correct integration in an information system.


Docker registry first steps

Here at Octo, we are fond of Docker. Not because we completely master it, but because we don’t (yet). And as DevOps-minded guys, we like new perspectives in Dev / Ops relationship. Docker is mainly about this, shifting each other’s expectation. Now that the 0.7 and 0.8 releases are out, its production readiness has never been closer and it’s getting pretty exciting.

In a previous article, we’ve answered a few questions allowing to understand the basic concepts of Dockers, let’s play around with few Docker command lines and manage a local repository (also called registry).