6 books
—
1 voter
Microservices Books
Showing 1-50 of 183

by (shelved 81 times as microservices)
avg rating 4.22 — 5,143 ratings — published 2014

by (shelved 45 times as microservices)
avg rating 4.25 — 695 ratings — published

by (shelved 41 times as microservices)
avg rating 4.29 — 1,075 ratings — published

by (shelved 14 times as microservices)
avg rating 3.72 — 219 ratings — published

by (shelved 14 times as microservices)
avg rating 4.21 — 204 ratings — published

by (shelved 13 times as microservices)
avg rating 3.81 — 456 ratings — published 2016

by (shelved 11 times as microservices)
avg rating 4.09 — 68 ratings — published

by (shelved 11 times as microservices)
avg rating 4.01 — 100 ratings — published

by (shelved 10 times as microservices)
avg rating 4.17 — 117 ratings — published

by (shelved 10 times as microservices)
avg rating 4.15 — 5,759 ratings — published 2003

by (shelved 9 times as microservices)
avg rating 3.87 — 92 ratings — published

by (shelved 8 times as microservices)
avg rating 4.04 — 48 ratings — published

by (shelved 8 times as microservices)
avg rating 3.51 — 245 ratings — published

by (shelved 7 times as microservices)
avg rating 3.49 — 65 ratings — published

by (shelved 7 times as microservices)
avg rating 4.06 — 54 ratings — published

by (shelved 7 times as microservices)
avg rating 3.59 — 27 ratings — published

by (shelved 6 times as microservices)
avg rating 3.71 — 24 ratings — published

by (shelved 6 times as microservices)
avg rating 4.70 — 10,164 ratings — published 2015

by (shelved 6 times as microservices)
avg rating 4.59 — 672 ratings — published

by (shelved 5 times as microservices)
avg rating 4.14 — 43 ratings — published 2020

by (shelved 5 times as microservices)
avg rating 4.05 — 1,282 ratings — published 2013

by (shelved 5 times as microservices)
avg rating 3.41 — 92 ratings — published

by (shelved 4 times as microservices)
avg rating 4.26 — 777 ratings — published 2021

by (shelved 4 times as microservices)
avg rating 4.34 — 152 ratings — published

by (shelved 4 times as microservices)
avg rating 4.23 — 22 ratings — published

by (shelved 4 times as microservices)
avg rating 3.82 — 1,307 ratings — published

by (shelved 4 times as microservices)
avg rating 3.27 — 22 ratings — published

by (shelved 4 times as microservices)
avg rating 4.14 — 65 ratings — published

by (shelved 4 times as microservices)
avg rating 3.66 — 192 ratings — published

by (shelved 3 times as microservices)
avg rating 4.50 — 2 ratings — published 2023

by (shelved 3 times as microservices)
avg rating 4.17 — 23 ratings — published

by (shelved 3 times as microservices)
avg rating 4.23 — 88 ratings — published

by (shelved 3 times as microservices)
avg rating 4.41 — 471 ratings — published

by (shelved 3 times as microservices)
avg rating 4.16 — 717 ratings — published

by (shelved 3 times as microservices)
avg rating 4.05 — 114 ratings — published

by (shelved 3 times as microservices)
avg rating 4.31 — 13 ratings — published

by (shelved 3 times as microservices)
avg rating 3.95 — 44 ratings — published

by (shelved 3 times as microservices)
avg rating 3.59 — 69 ratings — published

by (shelved 3 times as microservices)
avg rating 4.04 — 113 ratings — published

by (shelved 3 times as microservices)
avg rating 4.12 — 1,542 ratings — published 2003

by (shelved 3 times as microservices)
avg rating 3.84 — 480 ratings — published 2010

by (shelved 3 times as microservices)
avg rating 3.78 — 55 ratings — published 2016

by (shelved 2 times as microservices)
avg rating 4.04 — 26 ratings — published

by (shelved 2 times as microservices)
avg rating 4.10 — 10 ratings — published

by (shelved 2 times as microservices)
avg rating 4.54 — 24 ratings — published

by (shelved 2 times as microservices)
avg rating 4.19 — 31 ratings — published

by (shelved 2 times as microservices)
avg rating 3.81 — 21 ratings — published

by (shelved 2 times as microservices)
avg rating 3.63 — 38 ratings — published

by (shelved 2 times as microservices)
avg rating 3.59 — 46 ratings — published

by (shelved 2 times as microservices)
avg rating 4.37 — 515 ratings — published
“Resilience versus Robustness.
Typically when we want to improve a system’s ability to avoid outages, handle failures gracefully when they occur and recover quickly when they happen, we often talk about resilience. (…) Robustness is the ability of a system that is able to react to expected variations, Resilience is having an organisation capable of adapting to things that have not been thought of, which could very well include creating a culture of experimentation through things like chaos engineering.
For example, we are aware a specific machine could die, so we might bring redundancy into our system by load-balancing an instance, that is an example of addressing Robustness. Resiliency is the process of an organisation preparing itself to the fact that it cannot anticipate all potential problems. An important consideration here is that microservices do not necessarily give you robustness for free, rather they open up opportunities to design a system in such a way that it can better tolerate network partitions, service outages, and the like. Just spreading your functionality over multiple separate processed and separate machines does not guarantee improved robustness, quite the contrary, it may just increase your surface area of failure.”
― Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
Typically when we want to improve a system’s ability to avoid outages, handle failures gracefully when they occur and recover quickly when they happen, we often talk about resilience. (…) Robustness is the ability of a system that is able to react to expected variations, Resilience is having an organisation capable of adapting to things that have not been thought of, which could very well include creating a culture of experimentation through things like chaos engineering.
For example, we are aware a specific machine could die, so we might bring redundancy into our system by load-balancing an instance, that is an example of addressing Robustness. Resiliency is the process of an organisation preparing itself to the fact that it cannot anticipate all potential problems. An important consideration here is that microservices do not necessarily give you robustness for free, rather they open up opportunities to design a system in such a way that it can better tolerate network partitions, service outages, and the like. Just spreading your functionality over multiple separate processed and separate machines does not guarantee improved robustness, quite the contrary, it may just increase your surface area of failure.”
― Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
“By breaking our application into individual, independently deployable processes, we open up a host of mechanisms to improve the robustness of our applications. By using microservices, we are able to implement a more robust architecture, because functionality is decomposed, that is, an impact in one area of functionality may not bring down the whole system, we also can focus our time and energy on those parts of the application that most require robustness, ensuring critical parts of our system remain operational.”
― Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
― Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith