Cargando…
Get your hands dirty on clean architecture : build 'clean' applications with code examples in Java /
Building for maintainability is key to keep development costs low (and developers happy). The second edition of "Get Your Hands Dirty on Clean Architecture" is here to equip you with the essential skills and knowledge to build maintainable software. Building upon the success of the first e...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Otros Autores: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Birmingham, UK :
Packt Publishing Ltd.,
2023.
|
| Edición: | Second edition. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a22000007i 4500 | ||
|---|---|---|---|
| 001 | OR_on1391114035 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr cnu|||unuuu | ||
| 008 | 230725s2023 enka o 001 0 eng d | ||
| 040 | |a ORMDA |b eng |e rda |e pn |c ORMDA |d EBLCP |d OCLCQ |d IEEEE |d UKMGB | ||
| 015 | |a GBC3H1776 |2 bnb | ||
| 016 | 7 | |a 021140711 |2 Uk | |
| 019 | |a 1390560073 | ||
| 020 | |a 9781805125914 | ||
| 020 | |a 1805125915 | ||
| 020 | |z 9781805128373 | ||
| 029 | 1 | |a AU@ |b 000075033556 | |
| 029 | 1 | |a UKMGB |b 021140711 | |
| 035 | |a (OCoLC)1391114035 |z (OCoLC)1390560073 | ||
| 037 | |a 9781805128373 |b O'Reilly Media | ||
| 037 | |a 10251299 |b IEEE | ||
| 050 | 4 | |a QA76.754 | |
| 082 | 0 | 4 | |a 005.1/2 |2 23/eng/20230725 |
| 049 | |a UAMI | ||
| 100 | 1 | |a Hombergs, Tom, |e author. | |
| 245 | 1 | 0 | |a Get your hands dirty on clean architecture : |b build 'clean' applications with code examples in Java / |c Tom Hombergs ; foreword by Gernot Starke. |
| 250 | |a Second edition. | ||
| 264 | 1 | |a Birmingham, UK : |b Packt Publishing Ltd., |c 2023. | |
| 300 | |a 1 online resource (168 pages) : |b illustrations | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 500 | |a Includes index. | ||
| 520 | |a Building for maintainability is key to keep development costs low (and developers happy). The second edition of "Get Your Hands Dirty on Clean Architecture" is here to equip you with the essential skills and knowledge to build maintainable software. Building upon the success of the first edition, this comprehensive guide explores the drawbacks of conventional layered architecture and highlights the advantages of domain-centric styles such as Robert C. Martin's Clean Architecture and Alistair Cockburn's Hexagonal Architecture. Then, the book dives into hands-on chapters that show you how to manifest a Hexagonal Architecture in actual code. You'll learn in detail about different mapping strategies between the layers of a Hexagonal Architecture and see how to assemble the architecture elements into an application. The later chapters demonstrate how to enforce architecture boundaries, what shortcuts produce what types of technical debt, and how, sometimes, it is a good idea to willingly take on those debts. By the end of this second edition, you'll be armed with a deep understanding of the Hexagonal Architecture style and be ready to create maintainable web applications that save money and time. Whether you're a seasoned developer or a newcomer to the field, "Get Your Hands Dirty on Clean Architecture" will empower you to take your software architecture skills to new heights and build applications that stand the test of time. | ||
| 505 | 0 | |a Cover -- Title Page -- Copyright -- Dedication -- Foreword -- Contributors -- Table of Contents -- Preface -- Chapter 1: Maintainability -- What does maintainability even mean? -- Maintainability enables functionality -- Maintainability generates developer joy -- Maintainability supports decision-making -- Maintaining maintainability -- Chapter 2: What's Wrong with Layers? -- They promote database-driven design -- They're prone to shortcuts -- They grow hard to test -- They hide the use cases -- They make parallel work difficult -- How does this help me build maintainable software? | |
| 505 | 8 | |a Chapter 3: Inverting Dependencies -- The Single Responsibility Principle -- A tale about side effects -- The Dependency Inversion Principle -- Clean Architecture -- Hexagonal Architecture -- How does this help me build maintainable software? -- Chapter 4: Organizing Code -- Organizing By Layer -- Organizing by feature -- An architecturally expressive package structure -- The role of dependency injection -- How does this help me build maintainable software? -- Chapter 5: Implementing a Use Case -- Implementing the domain model -- A use case in a nutshell -- Validating input | |
| 505 | 8 | |a The power of constructors -- Different input models for different use cases -- Validating business rules -- Rich versus anemic domain model -- Different output models for different use cases -- What about read-only use cases? -- How does this help me build maintainable software? -- Chapter 6: Implementing a Web Adapter -- Dependency Inversion -- Responsibilities of a web adapter -- Slicing controllers -- How does this help me build maintainable software? -- Chapter 7: Implementing a Persistence Adapter -- Dependency inversion -- Responsibilities of a persistence adapter -- Slicing port interfaces | |
| 505 | 8 | |a Slicing persistence adapters -- An example with Spring Data JPA -- What about database transactions? -- How does this help me build maintainable software? -- Chapter 8: Testing Architecture Elements -- The test pyramid -- Testing a domain entity with unit tests -- Testing a use case with unit tests -- Testing a web adapter with integration tests -- Testing a persistence adapter with integration tests -- Testing main paths with system tests -- How much testing is enough? -- How does this help me build maintainable software? -- Chapter 9: Mapping between Boundaries -- The "No Mapping" strategy | |
| 505 | 8 | |a The "Two-Way" mapping strategy -- The "Full" mapping strategy -- The "One-Way" mapping strategy -- When to use which mapping strategy? -- How does this help me build maintainable software? -- Chapter 10: Assembling the Application -- Why even care about assembly? -- Assembling via plain code -- Assembling via Spring's classpath scanning -- Assembling via Spring's Java Config -- How does this help me build maintainable software? -- Chapter 11: Taking Shortcuts Consciously -- Why shortcuts are like broken windows -- The responsibility of starting clean -- Sharing models between use cases | |
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a Software architecture. | |
| 650 | 0 | |a Web applications. | |
| 650 | 0 | |a Java (Computer program language) | |
| 655 | 0 | |a Electronic books. | |
| 700 | 1 | |a Starke, Gernot, |e writer of foreword. | |
| 776 | 0 | 8 | |i Print version: |a Hombergs, Tom |t Get Your Hands Dirty on Clean Architecture |d Birmingham : Packt Publishing, Limited,c2023 |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/9781805128373/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 938 | |a ProQuest Ebook Central |b EBLB |n EBL30623859 | ||
| 994 | |a 92 |b IZTAP | ||