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.
- reasons why you should adopt these new architectures;
- opportunities they provide;
- impacts for enterprises.
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.
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.
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: http://www.meetup.com/devopsch/
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.
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).
This article is the iOS counterpart of Romain’s recent article on tracking code quality with Sonar on Android.
The problematic remains the same: quality is often overlooked for mobile Apps and the cost of setting up a proper quality tracking environment is usually deemed too high. This article will focus on showing that, while the iOS platform is not as tooled as Android, it’s now fast and easy to track code quality on iOS projects.
Even though this has been possible in the past mostly using Java tools (see a preceding post on tracking iOS code quality with Jenkins), it has often been limited to big projects where a quality process has to be enforced (and sometimes some metrics were even part of the contract – even if I am not a big fan of this). The main limitation was in that case the time and expertise to set everything up.
This article follows a presentation we held at soft-shake last October.
On January 24th in São Paulo, Mathieu Despriée - Consultant and Senior Architect at OCTO Technology – gave a talk about the innovative practices the Web Giants use to apply: Amazon, Facebook, Google, Netflix and LinkedIn to name some.
Here are the video and the slides, covering the following topics:
Reduce the Time to Market;
Mitigate issues when dealing with growing traffic and high volumes of data;
Excellence and quality for the products.
- Video: http://www.youtube.com/watch?v=PGW631c4cO0
- Slides: http://www.slideshare.net/OCTOTechnology/minicourse-web-giants/
- Dedicated website to the Web Giants (in French): http://www.geantsduweb.com/