Feature team: beyond the buzzword

FT-kesako

The team organization is the core issue when scaling out agile methods to the company scale. Here, many may mention “feature teams” but often forget the true meaning of these two words!

You are willing to change your teams organization and understand the differences between a cross-functional team and a feature team? This article proposes a few approaches to understand these models, and more importantly to know which one to adopt.

Read more

Concatenate, Compress, Cache

When trying to optimize the performance of your website, there are three main elements that should be on your top priority list. Three very easy-to-implement steps that can have a great impact on your website load time.

These three methods are named concatenation, compression and cache. I’ve already talked about them in a previous talk (in French), but we’ll now cover them in full detail.

Read more

Software Craftsmanship: a culture to pass on

Software CraftsmanshipThe Manifesto for Software Craftsmanship is subheaded Raising the bar.

Indeed, we believe that this is the main issue at stake behind this movement’s motivations. To create products that rock, you need to rely on people who know how to do it, enjoy it, and always strive to do it better.

It’s not just about introducing a few practices. It’s a genuine culture of development aiming at changing the mentalities, the team operations and the company.

But you can’t decree a change of culture. So how can one introduce the values of Craftsmanship into one’s company so that they become a standard instead of an isolated case?

Read more

Volatile packaging container with Docker

We’ve been discussing a lot about Docker as a mean to build and expose Web applications, here is another way to use it as a native distribution package building tool.

You want to product deb and rpm package for applications written in Ruby, Nodes.js, Python… These technologies usually rely on specific packaging tools which need internet to work (gem for Ruby, npm for Node.js, pip or easy_install for Python).

Having a compiling chain or an internet access on a production server is bad for security reason so you must use a specific server.

It’s difficult to maintain different compiling chains on a single server. You have to manage different versions of different kinds of technologies. Moreover, provisioning a server just for that need has a cost you can’t always afford.

The solution is to use container. One container embeds one compilation chain. Docker can help you for that.

An other difficulty concerns the production of the rpm and deb packages. Some tools exist to do it simply like the Opscode’s Omnibus framework.

Our example combine Docker and Opscode’s Omnibus framework.

Let’s dig into more details by building a Capistrano package as a DEB (for Ubuntu Precise) and as a RPM (for Centos 6). Capistrano is a CLI Ruby application with some gems as prerequisites.

Read more

N°1 betting operator in Europe lets you dive in an immersive horse race

What if you could race like a jockey ?

It is now possible with “LeTrot 360 Digital Immersion“, an immersive experience created by PMU (N°1 parimutual operator in Europe) and OCTO Technology!

On the 25th november, our team was proudly on stage during the “J-60 Grand Prix d’Amérique” Countdown Gala to provide guests an immersive horse racing experience using Oculus Rift virtual reality headset.

Read more

Web Scale IT (Or, The Patterns of the Giants of the Web) in Gartner’s Top 10 for 2015

Gartner’s long-awaited  Top 10 strategic technological trends  for 20151 have just been released this month and, for the second consecutive year2, one our most cherished topics at OCTO is prominently featured. In Gartner terminology, what we call the Practices of the  Giants of the Web 3, 4 becomes Web-Scale IT , and is inspired by “large cloud services firms5, 6. Here, we offer a brief overview of this trend for 2015. Read more

Get an instant access to up-to-date metrics at low cost

Bank’s current systems and issues

Today, Retail and Private Banks’ Core Banking System (CBS) and Portfolio Management System (PMS) are strong assets. They have matured over the years and are often a very solid basis for the rest of the satellite IT systems. They are used to efficiently manage the basic core banking data, like clients, portfolios, their security composition, the pending orders, the market transactions and so on. Portfolio-level and bank-level consolidated metrics however are often based on long running algorithms and are therefore executed either during end of day batches or on-demand, meaning users’ have to work with more or less outdated data or data that is long to get.

The issue is that in recent years, banking has seen several shifts:

  • An ever faster market (more actors, algorithmic trading, easier access to information)
  • A growing pressure on returns. Clients want reliability, while banks need to lower their margins due to competition
  • A complexification of the products to try and manage risks while meeting clients growing sophistication
  • The increasing regulatory pressure impacting margins, efficiency and attractiveness

Read more