Fundamentals of Software Architecture
An Engineering Approach
Impossible d'ajouter des articles
Échec de l’élimination de la liste d'envies.
Impossible de suivre le podcast
Impossible de ne plus suivre le podcast
Fundamentals of Software Architecture
Acheter pour 44,88 €
Aucun moyen de paiement n'est renseigné par défaut.
Désolés ! Le mode de paiement sélectionné n'est pas autorisé pour cette vente.
-
Lu par :
-
Benjamin Lange
-
De :
-
Mark Richards
-
Neal Ford
À propos de cette écoute
Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture’s many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics.
Mark Richards and Neal Ford—hands-on practitioners who have taught software architecture classes professionally for years—focus on architecture principles that apply across all technology stacks. You’ll explore software architecture in a modern light, taking into account all the innovations of the past decade.
This book examines:
- Architecture patterns: the technical basis for many architectural decisions
- Components: identification, coupling, cohesion, partitioning, and granularity
- Soft skills: effective team management, meetings, negotiation, presentations, and more
- Modernity: engineering practices and operational approaches that have changed radically in the past few years
- Architecture as an engineering discipline: repeatable results, metrics, and concrete valuations that add rigor to software architecture
Vous êtes membre Amazon Prime ?
Bénéficiez automatiquement de 2 livres audio offerts.Bonne écoute !
Ces titres pourraient vous intéresser
Ce que les auditeurs disent de Fundamentals of Software Architecture
Moyenne des évaluations utilisateurs. Seuls les utilisateurs ayant écouté le titre peuvent laisser une évaluation.Commentaires - Veuillez sélectionner les onglets ci-dessous pour changer la provenance des commentaires.
-
Global2 out of 5 stars
-
Interprétation2 out of 5 stars
-
Histoire2 out of 5 stars
- Utilisateur anonyme
- 24/06/2022
Random bulshit language
The middle part, where you would think the meat is, is extremely shallow, basically a big hierarcical list of things superficially treated, with barely motivated judgements (except for the authors pet architectures). Reading the table of contents of this section will give you about as much insight as actually playing it.
Most of the book is delivered in long intricate sentences full of abstract lingo, which can especially be annoying in an audio format because you can't skim through it. The first part of the book is absolutely soporiphic.
The authors don't really care about making sense to the reader. Example: "The mediator topology is commonly used when you require control over the workflow of an event process, whereas the broker topology is used when you require a high degree of responsiveness and dynamic control over the processing of an event". This is not the conclusion, it is the introduction, you are not supposed to know what this architecture style is. Did you get the difference between "control over the workflow of an event process" and "dynamic control over the processing of an event"? It makes sense after having listened to the rest of the chapter, but at that point in time this sentence is just confusing.
Sometimes you are just doubtful of what you hear. Example: you are told the pipeline architecture is basically function composition, but for some unexplained reason the filters can't be tested in isolation and the system can't be distributed. Why??? Care to explain? There are actually distributed pipeline architectures, but when you hear that a filter is a reducer, you start to wonder if the author knows what they are talking about anyway.
I appreciated that the authors mention the fact that architecture is a people problem, but the way you are recommended to deal with is plain manipulation: you want an overworked developper to "squeeze" an unplanned architectural change in the middle of an iteration ? Call them by their name multiple times, don't tell them what to do but refer to the request as a favor and use their emotions to make them relate to you and want to help you get out of an embarassing situation... my jaw dropped!
Une erreur s'est produite. Réessayez dans quelques minutes.
Merci. Votre vote a été pris en compte.
Vous avez donné votre avis sur cette évaluation !
6 personnes ont trouvé cela utile
