- Capa dura: 656 páginas
- Editora: Addison-Wesley Professional; Edição: 1 (7 de março de 2013)
- Idioma: Inglês
- ISBN-10: 0321834577
- ISBN-13: 978-0321834577
- Dimensões do produto: 18,3 x 4,1 x 23,6 cm
- Peso de envio: 1,1 Kg
- Avaliação média: 1 avaliação de cliente
- Lista de mais vendidos da Amazon: no. 72,113 em Livros (Conheça o Top 100 na categoria Livros)
Implementing Domain-Driven Design (Inglês) Capa dura – 6 mar 2013
|Novo a partir de||Usado a partir de|
|Prazo||Valor Mensal (R$)||Total (R$)|
|2x sem juros||R$ 115,13||R$ 230,25|
|3x sem juros||R$ 76,75||R$ 230,25|
|4x sem juros||R$ 57,57||R$ 230,25|
|5x sem juros||R$ 46,05||R$ 230,25|
|6x sem juros||R$ 38,40||R$ 230,25|
Leia Enquanto Enviamos
Compre e comece a ler a amostra digital deste livro enquanto espera ele chegar. Saiba mais aqui.
Clientes que visualizaram este item também visualizaram
Faça download dos Aplicativos de Leitura Kindle Gratuitos e comece a ler eBooks Kindle nos mais populares smartphones, tablets e computadores pessoais. Para enviar o link de download para seu smartphone por SMS, use o formato internacional sem espaços (Código Internacional+DDD+Número. Exemplo: +551199999999)
Para receber o link de download digite seu celular:
Veja todos os livros com desconto aqui
Detalhes do produto
Descrição do Produto
Sobre o Autor
Avaliação de clientes
Principais avaliações de clientes
Ocorreu um problema para filtrar as avaliações agora. Tente novamente mais tarde.
Avaliações mais úteis de consumidores na Amazon.com
There's enough good material in the book for me to convince myself I needed to plow through it to the end; the writing was such that I had to force myself to do it. I'd really like to read a copy of this that had had the benefit of a good editor. It was verbose, and tended to belabor points that I thought had been pretty clearly conveyed in a few pages, so it took a while to get through it.
It's a fairly thorough overview of the DDD space, and I think it filled in some things I didn't get from Evans earlier book. I do question some of the breezy assertions that it was almost always best to opt for the purety of the model over implementation concerns, particularly around doing implementations on top of RDBMS persistence.
I think it was worth the read, but in comparison to other technical books I've read (and I read a lot of them), it was a lot more work to get through the prose than I think it needed to be.
This book explains DDD concepts on well-chosen domain problem - agile and SCRUM. Reader (who is very likely to have at least some experience with SCRUM) is going to feel comfortable with most of the examples that this book provides.
Another huge plus is that author stays pragmatic. Author knows that DDD touches lot of 'theoretical' concepts, so he often mentions real-world situations and advises how to compromise certain situations - how can be DDD fully or not-so-fully utilised within your business. If you're afraid of 'too many abstractions' then don't be - peek into table of contents and you will see that author explains DDD on very real and quite recent technologies/buzzwords like REST, CQCS, Hexagonal Architecture etc. Author also assumes that reader is rather new to the whole DDD thing and patiently explains things you were 'afraid to ask', like "What's the difference between DAO and Repository?", "Is it OK to put fine-grained queries to DAO and return Value Objects?" etc.
On the other hand - what's not so great about this book is its verbosity. I don't mind repeating important concepts (redundancy can be useful as we know it from Head First books for example), but I often felt like reading a novel. If I wanted to read a novel, I would buy a novel. Technical books should be brief and precise. I had the feeling that it was happening too often that author went too deep into the problem and I simply got bored way too many times. I think the useful content of this book would comfortably fit into 60% of its length.
Last, but not least, I'd like to exalt the book structure and formatting which was really good. Even Kindle versions gets properly formatted source code, which (unfortunately) still isn't standard.
I thought the order of chapters was a little strange with many concepts being talked about in depth before they were properly defined (I haven't read Evans' book, so that could have been the problem though). I can't wait to read a text book like this one day where the author doesn't try and redefine terms for concepts that already have perfectly good names, it made things confusing at times.
There's was definitely enough insightful stuff in there to make me glad that I made it through.