- File Size: 2278 KB
- Print Length: 66 pages
- Publication Date: January 6, 2014
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B00HNG8ZFQ
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Enabled
Amazon Best Sellers Rank:
#114,944 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #18 in Kindle Store > Kindle eBooks > Computers & Technology > Networking & Communications > System Administration > Distributed Systems & Computing
- #24 in Kindle Store > Kindle eBooks > Computers & Technology > Computer Science > Systems Analysis & Design
- #49 in Books > Computers & Technology > Computer Science > Systems Analysis & Design
Queue-based System Architecture: Build Scalable, Fault-tolerant Distributed Systems Kindle Edition
Kindle Feature Spotlight
Try Kindle Countdown Deals
Explore limited-time discounted eBooks. Learn more.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Showing 1-8 of 12 reviews
There was a problem filtering reviews right now. Please try again later.
The book is concise and can be read entirely in a couple of hours, however the information it contains was worth the time.
For those entirely new to building distributed systems in this way, will find this book is a fine introduction. The book, nonetheless, offers very little insights on implementation details, and I believe that, given how short it is, the author may have decided to add an entire section to demonstrate all these ideas in some way, perhaps using a product like RabbitMQ.
That been said, I felt quite satisfied with the book and its short, but rather useful advise.
My one suggestion for this book has to do with how one solves a certain sort of pesky problem in the real world: customers don't want to go to a web page and then get a message back via email, log into the website again, get another message, and so on: the Health Care Exchange example dodges this (likely) requirement. I'd say that's fair -- it would have cluttered things up. A nod in that direction and a hint or two ("We'd use this or that technique if we had to accommodate a user who wants 'service while he waits'") would have been helpful.
I'd say this is very good value for the money!
I would have liked to see a bit more treatment on testing components across the bus, but you can't have everything.
Even so, this is a normative reference I am now eagerly recommending to everyone I am introducing these topics to. (I'd happily buy print copies if I could so I could have leave them with people who would otherwise not go buy it and read it on a Kindle.)
This book was a refreshing change of pace from the gigantic tomes you usually find in this area.