Devops for Growth
121.0K views | +6 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
February 1, 2015 6:38 AM
Scoop.it!

Laws of Software Design | Java Code Geeks

Laws of Software Design | Java Code Geeks | Devops for Growth | Scoop.it
Software design just like any other engineering design endeavor, requires a fair amount of effort, experience, patience and knowhow in order to be done right. Based on Akin's Laws of Spacecraft Design I present our readers with a slightly modified list of what I believe are the basic "Laws of Software design" especially when you are dealing with customer oriented, "tailored" software product solutions. As this is considered a "basic" list, let me clarify that you are more than welcome to contrib
Mickael Ruau's insight:
  1. Software design is done with numbers. Analysis without numbers is only an opinion.
  2. To design software products right takes an infinite amount of effort. This is why it’s a good idea to design them to operate when some things are wrong.
  3. Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time.
  4. Your best design efforts will inevitably wind up being useless in the final design. Learn to live with the disappointment.
  5. (Miller’s Law) Three points determine a curve.
  6. (Mar’s Law) Everything is linear if plotted log-log with a fat magic marker.
  7. At the start of any design effort, the person who most wants to be team leader is least likely to be capable of it.
  8. In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.
  9. Not having all the information you need is never a satisfactory excuse for not starting the analysis.
  10. When in doubt, estimate. In an emergency, guess. But be sure to go back and clean up the mess when the real numbers come along.
  11. Sometimes, the fastest way to get to the end is to throw everything out and start over.
  12. There is never a single right solution. There are always multiple wrong ones, though.
  13. Design is based on requirements. There’s no justification for designing something one bit “better” than the requirements dictate.
  14. (Edison’s Law) “Better” is the enemy of “good”.
  15. (Shea’s Law) The ability to improve a design occurs primarily at the interfaces. This is also the prime location for screwing it up.
  16. The previous people who did a similar analysis did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their analysis over yours. There is especially no reason to present their analysis as yours.
  17. Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though.
  18. The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you’ve screwed up.
  19. A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.
  20. (Larrabee’s Law) Half of everything you hear in a classroom is crap. Education is figuring out which half is which.
  21. When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
  22. The schedule you develop will seem like a complete work of fiction up until the time your customer fires you for not meeting it.
  23. It’s called a “Work Breakdown Structure” because the Work remaining will grow until you have a Breakdown, unless you enforce some Structure on it.
  24. (Bowden’s Law) Following a testing failure, it’s always possible to refine the analysis to show that you really had negative margins all along.
  25. (Montemerlo’s Law) Don’t do nuthin’ dumb.
  26. (Varsi’s Law) Schedules only move in one direction.
  27. (Heinlein’s Law) There ain’t no such thing as a free lunch.
  28. (von Tiesenhausen’s Law of Program Management) To get an accurate estimate of final program requirements, multiply the initial time estimates by pi, and slide the decimal point on the cost estimates one place to the right.
  29. (von Tiesenhausen’s Law of Engineering Design) If you want to have a maximum effect on the design of a new software system, learn to draw. Engineers always wind up designing the vehicle to look like the initial artist’s concept.
  30. (Mo’s Law of Evolutionary Development) You can’t get to the moon by climbing successively taller trees.
  31. (Atkin’s Law of Demonstrations) When the hardware is working perfectly, the really important visitors don’t show up.
  32. (Patton’s Law of Program Planning) A good plan violently executed now is better than a perfect plan next week.
  33. (Roosevelt’s Law of Task Planning) Do what you can, where you are, with what you have.
  34. (de Saint-Exupery’s Law of Design) A designer knows that he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.
  35. Any run-of-the-mill engineer can design something which is elegant. A good engineer designs systems to be efficient. A great engineer designs them to be effective.
  36. (Henshaw’s Law) One key to success in a mission is establishing clear lines of blame.
  37. Capabilities drive requirements, regardless of what the systems engineering textbooks say.
  38. Do not reinvent the wheel if you want to keep a new manned program affordable and on schedule.
No comment yet.
Scooped by Mickael Ruau
February 1, 2015 6:28 AM
Scoop.it!

High Availability for Web applications | Java Code Geeks

High Availability for Web applications | Java Code Geeks | Devops for Growth | Scoop.it
Redundancy and failover are techniques used to achieve high availability. Redundancy is achieved by having multiple copies of your server. Instead of 1 apache web server, you have two. One is the active server. The active server is monitered and if for some reason it fails, you failover to the 2nd server which becomes active. Another approach is to use a cluster of active servers as is done in a tomcat clusters. All servers are active. A load balancer distributes load among the members of the cluster. If one or two member of the cluster go down, no users are affects because other servers continue processing. Of course, the load balancer can become a point of failure and needs redundancy and failover.
No comment yet.
Scooped by Mickael Ruau
January 12, 2015 3:54 AM
Scoop.it!

Implementing Hypermedia

Implementing Hypermedia | Devops for Growth | Scoop.it
Designing, implementing, and maintaining APIs for the Web is more than a challenge; for many companies, it is an imperative. This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges, and taking the long view on maintaining public APIs on the Web over time. Along the way there are interviews with influential individuals and even a suggested reading list on APIs and related topics.

This InfoQ article is part of the series “Web APIs From Start to Finish”.
No comment yet.
Scooped by Mickael Ruau
January 5, 2015 4:44 AM
Scoop.it!

L'utilisation compte plus que la Taille

L'utilisation compte plus que la Taille | Devops for Growth | Scoop.it
L'utilisation de la taille pour la définition des microservices est une métrique inadaptée et inutile pour déterminer si un service possède les bonnes responsabilités, dit Jeppe Cramon dans une série de billets de blog qui clarifient sa vision sur les microservices et les problématiques de couplage qu'il trouve dans la communication synchrone bidirectionnelle.
No comment yet.
Scooped by Mickael Ruau
December 26, 2014 3:40 AM
Scoop.it!

Le rôle de l’architecte Agile - Jean-René Rousseau / Mathieu Boisvert…

La problématique des rôles périphériques aux équipes Scrum est une problématique que l'ensemble des organisations se doivent de comprendre et de gérer. Dans les dernières années on a beaucoup parlé du rôle du chargé de projet mais assez peu de celui de l'architecte qui, comme le chargé de projet, détient une position de fort leadership, mais se demande comment maintenant utiliser ce leadership dans un contexte d'agilité et d'auto-organisation des équipes.

Au cours de cette présentation, Jean-René, Frédérick et Mathieu présentent les principaux impacts de l'agilité sur le rôle de l'architecte et offriront des pistes de solutions quant à la façon de conduire la phase d'architecture et d'interagir pour les architectes avec les équipes.
No comment yet.
Scooped by Mickael Ruau
December 19, 2014 3:22 AM
Scoop.it!

The "Sashimi Method" for Building Software - 3Back Scrum & Agile Blog

The "Sashimi Method" for Building Software - 3Back Scrum & Agile Blog | Devops for Growth | Scoop.it
In this blog I will discuss one part of the puzzle, the Sashimi Method of incremental development, which has been around a long time. I first heard of it in the early 1990s, in the context of RUP (the Rational Unified Process), a high-ceremony agile process that focused its development on Use Cases. It was introduced to me again, in the late 1990s, as a way to understand XP (eXtreme Programming). And again, in the early 2000s, by Ken Schwaber, as the preferred way to develop software within a Scrum Team. And it’s baked into the current Software Craftsmanship movement, as part of developing Clean Code…
No comment yet.
Scooped by Mickael Ruau
December 15, 2014 4:12 AM
Scoop.it!

Que signifie idempotent dans REST ?

Que signifie idempotent dans REST ? | Devops for Growth | Scoop.it
Au fil des années, il a été dit beaucoup de choses sur REST et ses avantages perçus sur les autres approches, avec l'idempotence souvent considéré comme étant un concept compris par tous, mais qui n'a généralement pas été traité de manière exhaustive. Cependant, une récente publication sur la liste de diffusion Service Oriented Architecture a généré beaucoup de discussion autour d'un concept que beaucoup semblaient assumer assez simple.
No comment yet.
Scooped by Mickael Ruau
December 4, 2014 8:53 AM
Scoop.it!

Les limites (boundaries) des modules dans l'architecture Logicielle

Les limites (boundaries) des modules dans l'architecture Logicielle | Devops for Growth | Scoop.it
Les systèmes logiciels sont sillonnés par les limites (Boundaries), le code de part et d’autre de ces limites est bien différent. Des exemples de limites sont par exemple la limite entre le module definissant les objets du domaine et le module du mecanisme de livraison, ou encore la limite entre les vues et les modèles dans un module MVC.

Pour chacun de ces modules, un coté est abstrait et un coté est concret. Par exemple, le mécanisme de livraison est un coté concret,  et le module des objets d’affaires quand à lui, est abstrait.

Nous avons vu aussi dans le dernier article sur l’architecture, que tout le code source pointe vers l’extérieur depuis le côté concret vers le côté abstrait.
Mickael Ruau's insight:

Ceci est en fait une règle fondamentale de la conception orientée objet :

Les dépendances du code source code qui traversent la limite doivent pointer vers les abstractions à l’extérieur du cote concret. Ceci est l’un des aspects du « Principe d’inversion de contrôle »!

En mettant au clair la notion des limites dans une architecture orientée objet, et en spécifiant quelques notions de l’architecture de la couche de base de données,  il nous sera maintenant facile de répondre a la question posée a la fin du dernier post, soit  la séparation de la base de données dans une architecture modulaire. Ceci sera le sujet de notre prochain Post!

No comment yet.
Scooped by Mickael Ruau
December 4, 2014 8:49 AM
Scoop.it!

L'architecture Agile : L'architecture Orientée Objet, ou l'architecture par Cas D'utilisation

L'architecture Agile : L'architecture Orientée Objet, ou l'architecture par Cas D'utilisation | Devops for Growth | Scoop.it
Qu’est ce que les termes MVC, Base de données, Langage de Programmation, Framework, Editeur, SOA, Service Layer, REST etc. disent pour vous? est ce que ces termes la définissent l’architecture?  Non! Ces termes représentent des Outils. De la même façon que sur le plan de construction d’une maison, vous ne voyez pas la pelle et le marque du béton qui va être utilisée, vous ne devez pas voir dans l’architecture d’un logiciel les termes ci dessous.

L’architecture d’un système est une affaire d’Utilisation. Elle doit exposer clairement l’intention du système, et non les outils avec lesquels ce dernier va être construit.

Imaginez l’architecture d’une librairie ou d’un centre culturel, vous regardez le plan et vous voyez des salles de lecture ou les lecteurs peuvent calmement lire et faire leur recherche, vous voyez des petits espaces éclairées avec des fauteuils pour prendre une petite pause, et des chambres pleines d’étagères de livres. Que voyez vous dans l’architecture d’une librairie? Vous voyez Une librairie!
No comment yet.
Scooped by Mickael Ruau
November 24, 2014 5:31 PM
Scoop.it!

Gestion multisites - Retours d'expérience et solutions avec le CMS Am…

Les projets multisites sont de plus en plus nombreux, les entreprises et institutions souhaitent rationaliser les coûts et optent en priorité pour un socle technique modulable et évolutif capable de motoriser rapidement et simplement de nouveaux sites à moindre coût. Partage de contenu multisites, atelier de déclinaison de charte graphique, reprise des contenus existants...

No comment yet.
Scooped by Mickael Ruau
November 13, 2014 5:13 AM
Scoop.it!

Build Simplicity into a System with Simple Event-Driven Components

Build Simplicity into a System with Simple Event-Driven Components | Devops for Growth | Scoop.it
Use events for interactions between small business components to bring simplicity to a system, Russ Miles recently suggested talking about Coding Simple Event-Driven Components for Agile Software.

This talk is a follow-up on his talk a month earlier, Events bring Simplicity to a System's Architecture, where Russ laid the foundation for his ideas about simplicity; an architecture where small components collaborate with each other by exchanging events.
No comment yet.
Scooped by Mickael Ruau
November 12, 2014 3:06 AM
Scoop.it!

Implementing Hexagonal Architecture using Life Preserver and Spring Framework

Implementing Hexagonal Architecture using Life Preserver and Spring Framework | Devops for Growth | Scoop.it
We have all been there, the moment when someone asks you to make a change in the software, a change that you know you can’t do, at least not without a lot of effort, Russ Miles started his presentation at a recent meeting with the London Spring user group.
Russ calls this “the inconvenient truth of the killer change”; when you realise that the different assumptions about how the system or software will evolve was wrong and that you have to answer with some bad news.

Helping with this problem, Russ shares some techniques he uses when developing Java and Spring applications that helps him experience this moment less often. What he wants from a system is adaptability. The real world changes and we want to adapt to this, but the software we build is often less adaptable than we are as developers.
No comment yet.
Scooped by Mickael Ruau
November 7, 2014 5:04 AM
Scoop.it!

Domain-Driven Design with Onion Architecture

Domain-Driven Design with Onion Architecture | Devops for Growth | Scoop.it
Domain-Driven Design (DDD) together with Onion Architecture is a combination that Wade Waldron believes has increased his code quality dramatically since he started using it a few years back. Using DDD was a kick-off but together with Onion architecture he found his code to be more readable and understandable, and far easier to maintain.
Mickael Ruau's insight:

One way of verifying a design is to test different scenarios, e.g. what happens if a new database or user interface technology is asked for. By carefully following DDD and the Onion architecture principles Wade thinks it will be possible to accommodate these kinds of changes.

Alistair Cockburn presented his Hexagonal Architecture 2005 as a solution to problems with th e.g. traditional layering, coupling and entanglement.

Russ Miles did a presentation about his Life Preserver ideas, based on the Hexagonal architecture, last year.

A third variant is Clean Architecture by Robert C. Martin, which he talked about last year.

No comment yet.
Scooped by Mickael Ruau
February 1, 2015 6:30 AM
Scoop.it!

Keep As Much Stuff As Possible In The Application Itself | Bozho's tech blog

Keep As Much Stuff As Possible In The Application Itself | Bozho's tech blog | Devops for Growth | Scoop.it
I have always strived to keep as much stuff as possible in the application itself. NoSQL store? Embedded, please. Message queue? Again. URL rewrites – your web framework does that. Application server configurations? None, if possible, you can do them per-application. Modifications of the application server startup script? No, thanks. Caching? It’s in-memory anyway, why would you need a separate process. Every external configuration needed goes to a single file that resides outside the application, and Ops (or devs, or devops) can change that configuration. No more hidden stones to find in /usr/appconf, apache or whatever. Consolidate as much as possible in the piece that you are familiar and experienced with – the code.
Mickael Ruau's insight:

The main purpose of all that is to improve maintainability and manageability. You have a lot of tools, infrastructure and processes around your code, so make use of them for as much as possible.

No comment yet.
Scooped by Mickael Ruau
January 27, 2015 2:55 AM
Scoop.it!

REST Easy: API Design, Evolution, and Connection | WSO2 Inc

REST Easy: API Design, Evolution, and Connection | WSO2 Inc | Devops for Growth | Scoop.it
RESTful design increases API performance, reduces development effort, and minimizes operational support burden. By conforming web applications, web services, and web APIs with proven RESTful constraints, teams can create systems as scalable, pervasive, and prolific as The Web itself. Because REST requires a new development mindset, many API implementations are not truly based on REST constraints and principles, and do not exhibit expected scalability, evolvability, and interoperability. By following a few best practices and selecting RESTful tooling, teams can easily design, evolve, and connect RESTful APIs.
No comment yet.
Scooped by Mickael Ruau
January 9, 2015 2:56 AM
Scoop.it!

Roy Fielding on Versioning, Hypermedia, and REST

Roy Fielding on Versioning, Hypermedia, and REST | Devops for Growth | Scoop.it
Recently Roy took some time while traveling between standards meetings to answer a series of questions on a topic that often starts debates; Versioning on the Web. He also talked about why hypermedia is a requirement in his REST style, the process of designing network software that can adapt over time, and the challenge of thinking at the scale of decades.
No comment yet.
Scooped by Mickael Ruau
January 2, 2015 4:41 AM
Scoop.it!

Entretien avec Leslie Lamport : Systèmes Distribués et Precise Thinking

Entretien avec Leslie Lamport : Systèmes Distribués et Precise Thinking | Devops for Growth | Scoop.it
Leslie Lamport est l’auteur d’articles parmi les plus cités dans le domaine de l’informatique. Il a remporté un Turing Award en 2013 pour ses travaux séminaux sur les systèmes concurrents et distribués. Cet article est le résumé d’un entretien que Leslie a accordé à Software Engineering Radio au cours duquel il a évoqué ses premiers travaux sur les systèmes distribués et rappelé l’importance du "Precise Thinking" dans le cadre de la programmation.
No comment yet.
Scooped by Mickael Ruau
December 23, 2014 3:39 AM
Scoop.it!

Les fondements de l'Agilité

Les fondements de l'Agilité | Devops for Growth | Scoop.it
Le premier fondement de l’agilité sont les personnes. En agilité, nous entendons parler beaucoup de « l’équipe » en tant qu’unité, ceci peut donner l’impression que l’individu n’est pas concernée. Je pense que c’est tout à fait le contraire.

L’agilité reconnaît l’authenticité de chaque individu au lieu de considérer que c’est une « ressource ».
La valeur la plus importante de chaque individu est dans ses interactions et sa collaboration. Pour cette raison, les équipes agiles sont formées de différents « rôles » (développeurs, designers, testeurs, etc.) qui proviennent de diverses unités fonctionnelles.
Mickael Ruau's insight:

Qualité : "

  • Les bonnes architectures ne sont pas définies a l’avance mais émergent au fur et a mesure que le développement avance."
No comment yet.
Scooped by Mickael Ruau
December 18, 2014 3:11 AM
Scoop.it!

Améliorez votre API REST avec les hypermédias

Améliorez votre API REST avec les hypermédias | Devops for Growth | Scoop.it
Les liens hypermédia suppriment la partie inhérente qui restait dans le client :

Les liens montrent comment les ressources sont liées les unes aux autres
Les liens montrent comment interagir avec la ressource dans le contexte et les actions possibles
Les liens activent dynamiquement l'ajout et la suppression de commande selon le contexte
No comment yet.
Scooped by Mickael Ruau
December 15, 2014 3:05 AM
Scoop.it!

Pourquoi certaines Web APIs ne sont-elles pas RESTful et ce qui peut être fait à ce sujet

Pourquoi certaines Web APIs ne sont-elles pas RESTful et ce qui peut être fait à ce sujet | Devops for Growth | Scoop.it
Beaucoup de concepteurs de Web APIs présentent leurs APIs comme étant RESTful. Pourtant celles-ci ont souvent peu à voir avec REST. Que doit-il être fait pour que l’API d’un Web service soit réellement RESTful ?
Mickael Ruau's insight:

Roy Fielding a exprimé sa frustration au sujet d’implémentations d’APIs RESTful il y a plusieurs années, informant à cette occasion les concepteurs d’APIs que quelques règles devaient être respectées pour qu’une API puisse être qualifiée de RESTful, règles que nous rappelons brièvement ici :

  • Une API REST ne devrait pas être dépendante d’un protocole de communication.
  • Une API REST ne devrait pas apporter de modification aux protocoles de communication.
  • Les efforts consacrés aux aspects descriptifs d’une API REST devraient porter le plus souvent possible sur la définition de media types utilisés pour représenter des ressources et piloter l’état de l’application.
  • Une API REST ne doit pas fixer de noms pour les ressources et les hiérarchies (ce qui constituerait un couplage évident entre les clients et le serveur).
  • Une API REST ne devrait pas exposer de ressource “typée” significative au client.
  • Il devrait être possible d’accéder à une API REST sans aucune autre connaissance a priori que l’URI initiale (bookmark).
No comment yet.
Scooped by Mickael Ruau
December 4, 2014 8:49 AM
Scoop.it!

L'architecture Agile : L'architecture Orientée Objet, ou l'architecture par Cas D'utilisation

L'architecture Agile : L'architecture Orientée Objet, ou l'architecture par Cas D'utilisation | Devops for Growth | Scoop.it
Qu’est ce que les termes MVC, Base de données, Langage de Programmation, Framework, Editeur, SOA, Service Layer, REST etc. disent pour vous? est ce que ces termes la définissent l’architecture?  Non! Ces termes représentent des Outils. De la même façon que sur le plan de construction d’une maison, vous ne voyez pas la pelle et le marque du béton qui va être utilisée, vous ne devez pas voir dans l’architecture d’un logiciel les termes ci dessous.

L’architecture d’un système est une affaire d’Utilisation. Elle doit exposer clairement l’intention du système, et non les outils avec lesquels ce dernier va être construit.

Imaginez l’architecture d’une librairie ou d’un centre culturel, vous regardez le plan et vous voyez des salles de lecture ou les lecteurs peuvent calmement lire et faire leur recherche, vous voyez des petits espaces éclairées avec des fauteuils pour prendre une petite pause, et des chambres pleines d’étagères de livres. Que voyez vous dans l’architecture d’une librairie? Vous voyez Une librairie!
No comment yet.
Scooped by Mickael Ruau
November 26, 2014 4:36 AM
Scoop.it!

Multisites are a Bad Idea for Many Sites

Multisites are a Bad Idea for Many Sites | Devops for Growth | Scoop.it
As open source becomes more and more popular, we see organizations rolling out many sites across their organization. As they try to manage them, many of them turn to "multisite" networks.

In short, a "multisite" allows you to run many sites from a single codebase. The idea is that you can update the codebase once and automatically apply those changes to all your site. In theory, it's a great idea. In practice, it often causes more problems than it solves.

In this blog post, I'll explain why you should think very carefully before setting up a multisite network. No matter what software you use, there are often better alternatives.
No comment yet.
Scooped by Mickael Ruau
November 17, 2014 2:24 AM
Scoop.it!

Screaming Architecture | 8th Light

So what does the architecture of your application scream? When you look at the top level directory structure, and the source files in the highest level package; do they scream: Health Care System, or Accounting System, or Inventory Management System? Or do they scream: Rails, or Spring/Hibernate, or ASP?
No comment yet.
Scooped by Mickael Ruau
November 13, 2014 3:13 AM
Scoop.it!

Events bring Simplicity to a System's Architecture

Events bring Simplicity to a System's Architecture | Devops for Growth | Scoop.it
Using events for interactions between small business components can bring simplicity to a system's architecture, Russ Miles explained last week when talking about Architectural Simplicity through Events.

Simplicity really matters, Barbara Liskov said in a keynote at QCon London 2013, and Russ Miles, a Principal Consultant, strongly agrees. His experience is that teams often are slowed down by the increasing size and complexity of the code they write, and he believes that architecturally led simplicity is the best way to help teams keep their momentum and speed up.
No comment yet.
Scooped by Mickael Ruau
November 7, 2014 5:12 AM
Scoop.it!

Uncle Bob: Architecture is About Intent, not Frameworks

Uncle Bob: Architecture is About Intent, not Frameworks | Devops for Growth | Scoop.it

Architecture is about intent, we have made it about frameworks and details, Robert C. Martin, "Uncle Bob", stated earlier at this year’s DDD Exchange Day in London.

Robert refers to an architecture model described in the book Growing Object-Oriented Software Guided by Tests, (similar to the Hexagonal architecture), which describes an architecture with three zones with dependencies going only one way, from the volatile parts towards the more stable parts:
(...)
Robert notes that this model fails to describe what he regards as a key aspect; architecture is about intent, what the application does. He thinks we focus too much on details and frameworks and have made them the centre of our systems.

Mickael Ruau's insight:

To deal with this shortage Robert goes back to a book by Ivar Jacobson, "Object-Oriented Software Engineering, A Use Case Driven Approach" from 1992 where Ivar is defining a mechanism for application architecture based on small use cases without details.
Ivar introduces three types of objects, that fits naturally in the architecture model, and described by Robert as:

  • Interactors that understands the use cases and has application specific business rules.
  • Entities with the business rules, used by the Interactors.
  • Boundary objects that transfer data between the external world and the Interactors.

A significant advantage with this model, Robert claims, is that it's a very testable model; it can be tested without any dependency on infrastructure by just sending and receiving data structures trough the boundary objects.

No comment yet.