 Your new post is loading...
 Your new post is loading...
|
Scooped by
Mickael Ruau
November 6, 2014 3:11 PM
|
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.
|
Scooped by
Mickael Ruau
October 9, 2014 3:59 AM
|
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.
|
Scooped by
Mickael Ruau
October 2, 2014 6:13 AM
|
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
|
Scooped by
Mickael Ruau
October 2, 2014 3:18 AM
|
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.
|
Scooped by
Mickael Ruau
July 9, 2014 3:44 PM
|
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.
|
Scooped by
Mickael Ruau
July 9, 2014 3:40 PM
|
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 …
|
Scooped by
Mickael Ruau
July 9, 2014 3:35 PM
|
|
Scooped by
Mickael Ruau
June 16, 2014 1:40 AM
|
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…
|
Scooped by
Mickael Ruau
June 15, 2014 12:26 PM
|
In the semiconductor industry, Design For Testability (DFT) is an essential part of the architecture and design of components. Software designers on the other …
|
Scooped by
Mickael Ruau
May 26, 2014 5:36 PM
|
|
Scooped by
Mickael Ruau
May 4, 2014 5:59 AM
|
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.
|
Scooped by
Mickael Ruau
May 2, 2014 9:06 AM
|
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.
|
Scooped by
Mickael Ruau
March 21, 2014 11:18 AM
|
"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.
|
|
Scooped by
Mickael Ruau
October 11, 2014 6:44 PM
|
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.
|
Scooped by
Mickael Ruau
October 9, 2014 3:56 AM
|
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).
|
Scooped by
Mickael Ruau
October 2, 2014 6:12 AM
|
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.
|
Scooped by
Mickael Ruau
July 9, 2014 3:47 PM
|
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.
|
Scooped by
Mickael Ruau
July 9, 2014 3:41 PM
|
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 …
|
Scooped by
Mickael Ruau
July 9, 2014 3:40 PM
|
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 …
|
Scooped by
Mickael Ruau
June 21, 2014 4:19 AM
|
Ceci est une traduction de la recommandation "Architecture of the World Wide Web, First Edition" du W3C, édition du 15 décembre 2004
|
Scooped by
Mickael Ruau
June 15, 2014 12:32 PM
|
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.
|
Scooped by
Mickael Ruau
June 15, 2014 12:09 PM
|
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.
|
Scooped by
Mickael Ruau
May 19, 2014 8:38 AM
|
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.
|
Scooped by
Mickael Ruau
May 2, 2014 9:09 AM
|
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.
|
Scooped by
Mickael Ruau
March 28, 2014 11:53 AM
|
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.
|