ISBN: 9798171340100 - domain-driven design in python: a practical guide to modeling complex business domains and building maintainable software architectures (6 risultati)

Taschenbuch. Condizione: Neu. Neuware.

Condizione: New. Print on Demand.

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condizione: new. Paperback. You already know Python. This book teaches you how to use it to build software that actually understands the business it serves. You'll learn to translate messy, real-world rules into clean entities, value objects, and aggregates - and to organize a growing system into bounded contexts that stay sane as your business scales.Picture this: a small feature request lands on your desk. It should take an afternoon. Instead, you spend three days hunting through tangled conditionals, guessing which of five places actually enforces the rule you need to change, and hoping you haven't broken something on the other side of the codebase.This is what happens when software drifts away from the business it was built to serve.Now imagine the opposite. A domain expert describes a new rule to you in plain language - and you already know exactly where it belongs. Your Shipment class enforces its own weight limit. Your Subscription knows when it can and can't be paused. Nothing breaks quietly somewhere else, because nothing was ever scattered in the first place.That's not luck. That's a model - one built deliberately, in conversation with the people who understand the business, and expressed faithfully in your code. This book walks you through building exactly that, one deliberate decision at a time.What's InsideThe philosophy behind Domain-Driven Design - and why Python is more than capable of itCollaborative techniques like event storming for uncovering hidden business rulesThe ubiquitous language: keeping your code and your conversations in syncBounded contexts and context mapping for taming complex, multi-team systemsTactical building blocks: entities, value objects, aggregates, and domain servicesDomain events, repositories, and factories for a fully decoupled architectureApplication layer patterns: CQRS, the Unit of Work, and clean cross-cutting concernsHexagonal architecture with SQLAlchemy, FastAPI/Flask, and message brokersTesting strategies that make refactoring a domain model safe, not scaryA practical playbook for introducing all of this into an existing legacy codebaseWho It's Meant ForThis book is for the Python developer who's tired of code that no longer makes sense to anyone - including its own author. Whether you're building something new or trying to rescue something old, if you've ever thought "there has to be a better way to organize this," you're exactly who this book was written for. Some comfort with Python classes and basic object-oriented concepts is assumed; no prior DDD experience is needed.Every system you'll ever touch is drifting one of two directions: toward clarity, or toward chaos. The gap between those two futures isn't talent. It's method.You can keep patching the same tangled logic, hoping nothing else breaks. Or you can open this book, learn to listen to your domain the right way, and start building software that actually holds up - feature after feature, year after year.Turn the page. Your next codebase is waiting to be built right. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condizione: new. Paperback. You already know Python. This book teaches you how to use it to build software that actually understands the business it serves. You'll learn to translate messy, real-world rules into clean entities, value objects, and aggregates - and to organize a growing system into bounded contexts that stay sane as your business scales.Picture this: a small feature request lands on your desk. It should take an afternoon. Instead, you spend three days hunting through tangled conditionals, guessing which of five places actually enforces the rule you need to change, and hoping you haven't broken something on the other side of the codebase.This is what happens when software drifts away from the business it was built to serve.Now imagine the opposite. A domain expert describes a new rule to you in plain language - and you already know exactly where it belongs. Your Shipment class enforces its own weight limit. Your Subscription knows when it can and can't be paused. Nothing breaks quietly somewhere else, because nothing was ever scattered in the first place.That's not luck. That's a model - one built deliberately, in conversation with the people who understand the business, and expressed faithfully in your code. This book walks you through building exactly that, one deliberate decision at a time.What's InsideThe philosophy behind Domain-Driven Design - and why Python is more than capable of itCollaborative techniques like event storming for uncovering hidden business rulesThe ubiquitous language: keeping your code and your conversations in syncBounded contexts and context mapping for taming complex, multi-team systemsTactical building blocks: entities, value objects, aggregates, and domain servicesDomain events, repositories, and factories for a fully decoupled architectureApplication layer patterns: CQRS, the Unit of Work, and clean cross-cutting concernsHexagonal architecture with SQLAlchemy, FastAPI/Flask, and message brokersTesting strategies that make refactoring a domain model safe, not scaryA practical playbook for introducing all of this into an existing legacy codebaseWho It's Meant ForThis book is for the Python developer who's tired of code that no longer makes sense to anyone - including its own author. Whether you're building something new or trying to rescue something old, if you've ever thought "there has to be a better way to organize this," you're exactly who this book was written for. Some comfort with Python classes and basic object-oriented concepts is assumed; no prior DDD experience is needed.Every system you'll ever touch is drifting one of two directions: toward clarity, or toward chaos. The gap between those two futures isn't talent. It's method.You can keep patching the same tangled logic, hoping nothing else breaks. Or you can open this book, learn to listen to your domain the right way, and start building software that actually holds up - feature after feature, year after year.Turn the page. Your next codebase is waiting to be built right. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…