Devops for Growth
121.0K views | +0 today
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'architecture'. Clear
Scooped by Mickael Ruau
November 6, 2014 3:11 PM
Scoop.it!

Microservices vs Bibliothèques Partagées

Microservices vs Bibliothèques Partagées | Devops for Growth | Scoop.it
Dans un article récent, Robert C. Martin conseille de démarrer avec des bibliothèques partagées et une architecture basée sur les plugins, et de n'introduire la ségrégation entre les services et les microservices uniquement que lorsque cela se révèle insuffisant.

Dans sa réponse, Giorgio Sironi invoque des contre-arguments, mettant en exergue les différences entre les interactions parmi les microservices et celles parmi les objets d'une application, et met en garde contre les coûts de migration vers les microservices d'une base de code existante.
No comment yet.
Scooped by Mickael Ruau
October 9, 2014 3:59 AM
Scoop.it!

TOGAF® Version 9.1 (90-Day Evaluation License) - I112

You may download TOGAF Version 9.1 under a free, personal, 90-day Evaluation License; and you may then go on to use it internally under a free, perpetual, Corporate License or a free, perpetual, Academic License, if you wish. Alternatively, you may take out an annual Commercial License.
No comment yet.
Scooped by Mickael Ruau
October 2, 2014 6:13 AM
Scoop.it!

Micro-services ? Qu'en est-il des Nano-services ?

Micro-services ? Qu'en est-il des Nano-services ? | Devops for Growth | Scoop.it
Plus tôt cette année, nous avons publié un article sur la récente montée des discussions autour du terme Micro-services et si cela représente une nouvelle approche pour l'architecture, ou comme certains le suggèrent, tel que Steve Jones, que c’est tout simplement SOA sous un autre nom. Compte tenu des commentaires dans l'article, il semble que la majorité des lecteurs (ou la majorité de ceux qui ont commenté) pensent que les Micro-services seraient pareils à SOA et qu’un nouveau terme n'est probablement pas nécessaire. Suite à cet article, Steve en a publié un autre où il explique comment les Micro-services sont simplement de la livraison orientée services et que les tentatives de l'éloigner de SOA n'ont aucun sens
No comment yet.
Scooped by Mickael Ruau
October 2, 2014 3:18 AM
Scoop.it!

Startup Architecture : Movidone

Startup Architecture : Movidone | Devops for Growth | Scoop.it
Lors de l'événement Azure Camp qui a eu lieu cet été, InfoQ FR a pu rencontrer les startups qui ont participé à la conférence et fait un retour d'expérience sur leurs systèmes de production. Voici donc un épisode de cette petite série, consacré à Movidone, avec Sylvain Lamarche, son CTO.
Xavier Guidis's comment, March 1, 2018 6:11 AM
Je ne recommande vraiment pas MoviDOne, cette société escroque ses clients. Dispo pour en parler
Scooped by Mickael Ruau
July 9, 2014 3:44 PM
Scoop.it!

An Architecturally-Evident Coding Style | Javalobby

An Architecturally-Evident Coding Style | Javalobby | Devops for Growth | Scoop.it

Okay, this is the separate blog post that I referred to in Software architecture vs code. What exactly do we mean by an "architecturally-evident coding style"? I built a simple content aggregator for the local tech community here in Jersey called techtribes.je, which is basically made up of a web server, a couple of databases and a standalone Java application that is responsible for actually aggegrating the content displayed on the website. You can read a little more about the software architecture attechtribes.je - containers. The following diagram is a zoom-in of the standalone content updater application, showing how it's been decomposed.

No comment yet.
Scooped by Mickael Ruau
July 9, 2014 3:40 PM
Scoop.it!

Three Flaws in Software Design - Part 2: Not Making the Code Easy to Change - TechTalksHub

Three Flaws in Software Design - Part 2: Not Making the Code Easy to Change - TechTalksHub | Devops for Growth | Scoop.it
In part two of the series, Jeremy Walker & Max Kanat-Alexander discuss the second Flaw of Software Design, “Not Making the Code Easy to Change,” from Max’s book Code Simplicity: The Fundamentals of Software. Video: Three Flaws in Software Design - Part 2: Not Making the Code Easy to Change In part two of the …
No comment yet.
Scooped by Mickael Ruau
July 9, 2014 3:35 PM
Scoop.it!

Identifying Architectural Elements in Current Systems | Javalobby

Identifying Architectural Elements in Current Systems | Javalobby | Devops for Growth | Scoop.it

Simon recently talked about the gap between Software Architecture and Code and how to close this with architecturally-evident coding. He's also creating tools to allow Software Architecture to be expressed as code.

No comment yet.
Scooped by Mickael Ruau
June 16, 2014 1:40 AM
Scoop.it!

Cours de Génie Logiciel / ESIEA 2013-2014

Slides du cours de Génie Logiciel pour les étudiants de l'ESIEA, année 2013-2014. Le Génie Logiciel, c'est "l'ensemble des activités de conception et de mise e…
No comment yet.
Scooped by Mickael Ruau
June 15, 2014 12:26 PM
Scoop.it!

Designing Software For Testability: A forgotten design pattern

In the semiconductor industry, Design For Testability (DFT) is an essential part of the architecture and design of components. Software designers on the other …
No comment yet.
Scooped by Mickael Ruau
May 26, 2014 5:36 PM
Scoop.it!

[BreizhCamp] Slides de ma présentation // lyjia.net

[BreizhCamp] Slides de ma présentation // lyjia.net | Devops for Growth | Scoop.it

J’ai été ravie de pouvoir présenter ma session “Faire la conception en équipe sans architecte, non mais allô quoi” au BreizhCamp, à Rennes.

Mickael Ruau's insight:

Références non indiquées lors de la présentation

Les autres références sont indiquées dans la section bibliographie de mes slides.

No comment yet.
Scooped by Mickael Ruau
May 4, 2014 5:59 AM
Scoop.it!

Going Reactive: Event-Driven, Scalable, Resilient & Responsive Systems

Going Reactive: Event-Driven, Scalable, Resilient & Responsive Systems | Devops for Growth | Scoop.it
Jonas Bonér discusses how the four traits of reactive apps -Event-Driven, Scalable, Resilient and Responsive- impact app design, how they interact, and their supporting technologies and techniques.
No comment yet.
Scooped by Mickael Ruau
May 2, 2014 9:06 AM
Scoop.it!

Simple Made Easy

Simple Made Easy | Devops for Growth | Scoop.it
Rich Hickey emphasizes simplicity’s virtues over easiness’, showing that while many choose easiness they may end up with complexity, and the better way is to choose easiness along the simplicity path.
Mickael Ruau's insight:

Rich Hickey, the author of Clojure, is an independent software designer, consultant and application architect with over 20 years of experience in all facets of software development. Rich has worked on scheduling systems, broadcast automation, audio analysis and fingerprinting, database design, yield management, exit poll systems, and machine listening.

No comment yet.
Scooped by Mickael Ruau
March 21, 2014 11:18 AM
Scoop.it!

Microservices

Microservices | Devops for Growth | Scoop.it

"Microservices" - yet another new term on the crowded streets of software architecture.Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. We've seen many projects use this style in the last few years, and results so far have been positive, so much so that for many of our colleagues this is becoming the default style for building enterprise applications.

Mickael Ruau's insight:

In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare mininum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.

To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit.

No comment yet.
Scooped by Mickael Ruau
October 11, 2014 6:44 PM
Scoop.it!

Dossier SI : Urbaniser son système d'information, un mal pour un bien ? (2/2) | iTPro.fr

Dossier SI : Urbaniser son système d'information, un mal pour un bien ? (2/2) | iTPro.fr | Devops for Growth | Scoop.it
Que faire une fois la cartographie effectuée ?

Une fois l’ensemble du système cartographié, il s’agit de planifier l’ensemble des modifications à effectuer pour tendre vers un système cohérent et modulaire correspondant au métier de l’entreprise. D’un point de vue technique, il s’agit dès lors de migrer, en profitant de cette phase pour effectuer du nettoyage ou de la conversion de code tout en consolidant et mutualisant les serveurs afin d’utiliser l’ensemble de son environnement au maximum. On en profitera également pour diminuer les couches techniques et mettre en place de la communication entre les différentes applications.
No comment yet.
Scooped by Mickael Ruau
October 9, 2014 3:56 AM
Scoop.it!

TOGAF - Introduction

Downloads of the TOGAF documentation, including a printable PDF file, are available under license from the TOGAF information web site (www.opengroup.org/architecture/togaf). The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an Information Systems Architecture for use within that organization).
Mickael Ruau's insight:

The TOGAF documentation is freely available for viewing online without a license. Alternatively, the complete TOGAF documentation set may be downloaded and stored under license, as explained on the TOGAF information web site.

In either case, the TOGAF documentation may be used freely by any organization wishing to do so to develop an architecture for use within that organization. No part of it may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, for any other purpose including, but not by way of limitation, any use for commercial gain, without the prior permission of the copyright owners.

No comment yet.
Scooped by Mickael Ruau
October 2, 2014 6:12 AM
Scoop.it!

Modèles pour la Construction et le Déploiement de Microservices

Modèles pour la Construction et le Déploiement de Microservices | Devops for Growth | Scoop.it
La gestion de microservices implique de s'occuper de beaucoup de petits systèmes qui dialoguent entre eux et le provisionnement automatisé ainsi que l'automatisation de l'infrastructure sont cruciaux, a déclaré James Lewis en partageant les techniques et les pratiques qui l'ont aidé à gérer la complexité apportée par l'architecture microservice.

James, consultant pour ThoughtWorks, décrit l'origine des microservices comme la réaction à la manière dont nous avons construit des grosses applications monolithiques qui sont malaisées à changer, à tester et à gérer ; essentiellement, de gros tas de boue avec du code spaghetti entremêlé. La solution est de construire de plus petites choses et de les faire communiquer d'une manière ou d'une autre.

Pour James, les microservices signifient prendre une application importante, en identifier les contextes bornés et les capacités métier, et les diviser en prenant les données avec eux, c'est-à-dire des bases de données applicatives plutôt qu'une seule base de données d'intégration. La clé est de commencer au plus haut avec une map de contexte afin de comprendre le domaine métier.
No comment yet.
Scooped by Mickael Ruau
July 9, 2014 3:47 PM
Scoop.it!

Extremely Decoupled Architecture for Web Applications (EDAWA); Part 1: Vertical Decoupling | Javalobby

Extremely Decoupled Architecture for Web Applications (EDAWA); Part 1: Vertical Decoupling | Javalobby | Devops for Growth | Scoop.it

Ever see a company going out of business because it couldn't afford a complete redesign of a big application?

Ever wanted to switch a large application to a new technology stack in short, well defined steps?

Ever struggled understanding or changing an existing web application because its structure is complicated or not well defined at all?

Ever had trouble because the scalability of a web application is too limited as site traffic grows?

I have faced all these problems way too many times already. That is why I think its time to not change so much the tools (as this has never helped) but the way they are used.

Mickael Ruau's insight:

In this series of posts I would like to introduce an architectural pattern for web applications that is largely independent of any concrete implementation. I will be looking for an implementation for the Java world in a future post.

This work is by no means complete but an ongoing task. So I am very thankful for any kind of feedback.

No comment yet.
Scooped by Mickael Ruau
July 9, 2014 3:41 PM
Scoop.it!

Three Flaws in Software Design - Part 3: Being Too Generic - TechTalksHub

Three Flaws in Software Design - Part 3: Being Too Generic - TechTalksHub | Devops for Growth | Scoop.it
In part three of the series, Jeremy Walker & Max Kanat-Alexander discuss the third Flaw in Software Design, “Being Too Generic,” from Max’s book Code Simplicity: The Fundamentals of Software.Link to presentation: http://goo.gl/h73nY3 Video: Three Flaws in Software Design - Part 3: Being Too Generic In part three of the series, Jeremy Walker Max Kanat-Alexander discuss …
No comment yet.
Scooped by Mickael Ruau
July 9, 2014 3:40 PM
Scoop.it!

Three Flaws in Software Design - Part 1: Writing Code that isn't Needed - TechTalksHub

Three Flaws in Software Design - Part 1: Writing Code that isn't Needed - TechTalksHub | Devops for Growth | Scoop.it
In part one of the series, Jeremy Walker & Max Kanat-Alexander discuss the first Flaw of Software Design, “Writing Code that isn’t Needed,” from Max’s book Code Simplicity: The Fundamentals of Software. Video: Three Flaws in Software Design - Part 1: Writing Code that isn't Needed In part one of the series, Jeremy Walker Max …
No comment yet.
Scooped by Mickael Ruau
June 21, 2014 4:19 AM
Scoop.it!

Architecture du World Wide Web, Volume Un

Architecture du World Wide Web, Volume Un | Devops for Growth | Scoop.it

Ceci est une traduction de la recommandation "Architecture of the World Wide Web, First Edition" du W3C, édition du 15 décembre 2004

Mickael Ruau's insight:

Cette version française intègre toutes les corrections survenues depuis la parution de la recommandation. 

No comment yet.
Scooped by Mickael Ruau
June 15, 2014 12:32 PM
Scoop.it!

The Architecture of Open Source Applications

The Architecture of Open Source Applications | Devops for Growth | Scoop.it

Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.

Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think.

If you are a junior developer, and want to learn how your more experienced colleagues think, these books are the place to start. If you are an intermediate or senior developer, and want to see how your peers have solved hard design problems, these books can help you too.

Follow us on our blog at http://aosabook.org/blog/, or on Twitter at @aosabook and using the #aosa hashtag.

Mickael Ruau's insight:

Buy Volume II

IntroductionAmy Brown and Greg Wilson1.Scalable Web Architecture and Distributed SystemsKate Matsudaira2.Firefox Release EngineeringChris AtLee, Lukas Blakk, John O'Duinn, and Armen Zambrano Gasparnian3.FreeRTOSChristopher Svec4.GDBStan Shebs5.The Glasgow Haskell CompilerSimon Marlow and Simon Peyton-Jones6.GitSusan Potter7.GPSDEric Raymond8.The Dynamic Language Runtime and the Iron LanguagesJeff Hardy9.ITKLuis Ibanez and Brad King10.GNU MailmanBarry Warsaw11.matplotlibJohn Hunter and Michael Droettboom12.MediaWikiSumana Harihareswara and Guillaume Paumier13.MoodleTim Hunt14.nginxAndrey Alexeev15.Open MPIJeff Squyres16.OSCARJennifer Ruttan17.Processing.jsMike Kamermans18.PuppetLuke Kanies19.PyPyBenjamin Peterson20.SQLAlchemyMichael Bayer21.TwistedJessica McKellar22.YesodMichael Snoyman23.YoctoElizabeth Flanagan24.ZeroMQMartin SústrikBibliography

Buy Volume I

IntroductionAmy Brown and Greg Wilson1.AsteriskRussell Bryant2.AudacityJames Crook3.The Bourne-Again ShellChet Ramey4.Berkeley DBMargo Seltzer and Keith Bostic5.CMakeBill Hoffman and Kenneth Martin6.EclipseKim Moir7.GraphiteChris Davis8.The Hadoop Distributed File SystemRobert Chansler, Hairong Kuang, Sanjay Radia, Konstantin Shvachko, and Suresh Srinivas9.Continuous IntegrationC. Titus Brown and Rosangela Canino-Koning10.JitsiEmil Ivov11.LLVMChris Lattner12.MercurialDirkjan Ochtman13.The NoSQL EcosystemAdam Marcus14.Python PackagingTarek Ziadé15.Riak and Erlang/OTPFrancesco Cesarini, Andy Gross, and Justin Sheehy16.Selenium WebDriverSimon Stewart17.SendmailEric Allman18.SnowFlockRoy Bryant and Andrés Lagar-Cavilla19.SocialCalcAudrey Tang20.TelepathyDanielle Madeley21.Thousand ParsecAlan Laudicina and Aaron Mavrinac22.VioletCay Horstmann23.VisTrailsJuliana Freire, David Koop, Emanuele Santos, Carlos Scheidegger,Claudio Silva, and Huy T. Vo24.VTKBerk Geveci and Will Schroeder25.Battle For WesnothRichard Shimooka and David WhiteBibliography
License and Royalties

This work is made available under the Creative Commons Attribution 3.0 Unported license. Please see the full description of the license for details. All royalties from sales of these books will be donated to Amnesty International.

No comment yet.
Scooped by Mickael Ruau
June 15, 2014 12:09 PM
Scoop.it!

The Architecture of Open Source Applications: Selenium WebDriver

The Architecture of Open Source Applications: Selenium WebDriver | Devops for Growth | Scoop.it

Selenium is a browser automation tool, commonly used for writing end-to-end tests of web applications. A browser automation tool does exactly what you would expect: automate the control of a browser so that repetitive tasks can be automated. It sounds like a simple problem to solve, but as we will see, a lot has to happen behind the scenes to make it work.

Before describing the architecture of Selenium it helps to understand how the various related pieces of the project fit together. At a very high level, Selenium is a suite of three tools. The first of these tools, Selenium IDE, is an extension for Firefox that allows users to record and playback tests. The record/playback paradigm can be limiting and isn't suitable for many users, so the second tool in the suite, Selenium WebDriver, provides APIs in a variety of languages to allow for more control and the application of standard software development practices. The final tool, Selenium Grid, makes it possible to use the Selenium APIs to control browser instances distributed over a grid of machines, allowing more tests to run in parallel. Within the project, they are referred to as "IDE", "WebDriver" and "Grid". This chapter explores the architecture of Selenium WebDriver.

Mickael Ruau's insight:


This chapter was written during the betas of Selenium 2.0 in late 2010. If you're reading the book after then, then things will have moved forward, and you'll be able to see how the architectural choices described here have unfolded. If you're reading before that date: Congratulations! You have a time machine. Can I have some winning lottery numbers?

No comment yet.
Scooped by Mickael Ruau
May 19, 2014 8:38 AM
Scoop.it!

La genèse du modèle réactif

La genèse du modèle réactif | Devops for Growth | Scoop.it
Dans un précédent article, nous avons introduit un nouveau modèle de développement qui émerge de plus en plus : le modèle réactif.
Mickael Ruau's insight:

Dans un précédent article, nous avons introduit un nouveau modèle de développement qui émerge de plus en plus : le modèle réactif. C’est un modèle fondé sur la réaction à des événements déclenchés par les périphériques hardware (disque ou réseau essentiellement). Pourquoi seulement maintenant ?

L’objectif principal de ce modèle est la performance :

  • réduire la latence,
  • répondre plus vite
  • et gérer les pics de charges.

A cela s’ajoute la résilience et la scalabilité.

Pour en arriver là, il a fallu une succession d’étapes dans toutes les couches logicielles. Elles ne sont pas encore toutes terminées, mais c’est pour bientôt. 

No comment yet.
Scooped by Mickael Ruau
May 2, 2014 9:09 AM
Scoop.it!

(2) Tikhon Jelvis's answer to What are good ways to avoid bugs while programming? - Quora

(2) Tikhon Jelvis's answer to What are good ways to avoid bugs while programming? - Quora | Devops for Growth | Scoop.it
Tikhon Jelvis, consistency is all I ask 
For me, there are two main things which work very well together: keeping my codesimple and modular. These two core ideas are heavily helped by certain tools, most notably static types and functional programming.
Mickael Ruau's insight:

Simplicity is a pretty specific idea that too many people mistake for "easiness". Rich Hickey's talk "Simple Made Easy" illustrates this distinction particularly well. If you do not want to watch the talk, just remember that "simple" is not the same as "easy".

Basically, simple code does not do too much. It does not have too much internal structure: things are directly related to only a few other things, rather than having everything depend on everything. As much as possible, everything serves one concrete purpose.

No comment yet.
Scooped by Mickael Ruau
March 28, 2014 11:53 AM
Scoop.it!

CommonJS Spec Wiki

CommonJS Spec Wiki | Devops for Growth | Scoop.it

Welcome to CommonJS, a group with a goal of building up the JavaScript ecosystem for web servers, desktop and command line apps and in the browser.

Mickael Ruau's insight:

Un groupe pour unifier les frameworks javascripts. 

Participants : Narwhal, RequireJS, SproutCore, Wakanda, Node.js, curl.js, CouchDB...


NB : "QUnit's assertion methods follow the CommonJS Unit Testing specification, which was to some degree influenced by QUnit."

No comment yet.