Understanding distributed systems : Version 2.0.0 / Roberto Vitillo
Publisher: [S.l.] : Roberto Vitillo, 2022Edition: Second editionDescription: [XV],328 p. : il. b. y n. ; 23 cmISBN: 9781838430214Other title: Understanding distributed systems : What every developer should know about large distributed applicationsSubject(s): Sistemas operativos (Ordenadores)
Item type | Current location | Collection | Call number | Status | Date due | Barcode | Course reserves |
---|---|---|---|---|---|---|---|
![]() |
Biblioteca Universidad Europea del Atlántico Fondo General | No ficción | 004.451 ROB und | Checked out | 24/03/2023 | 4422 |
En cubierta: Understanding distributed systems: What every developer should know about large distributed applications
Communication -- Coordination -- Scalability -- Resilency -- Maintainability
Learning to build distributed systems is hard, especially if they are large scale. It's not that there is a lack of information out there. You can find academic papers, engineering blogs, and even books on the subject. The problem is that the available information is spread out all over the place, and if you were to put it on a spectrum from theory to practice, you would find a lot of material at the two ends but not much in the middle.
That is why I decided to write a book that brings together the core theoretical and practical concepts of distributed systems so that you don't have to spend hours connecting the dots. This book will guide you through the fundamentals of large-scale distributed systems, with just enough details and external references to dive deeper. This is the guide I wished existed when I first started out, based on my experience building large distributed systems that scale to millions of requests per second and billions of devices.
If you are a developer working on the backend of web or mobile applications (or would like to be!), this book is for you. When building distributed applications, you need to be familiar with the network stack, data consistency models, scalability and reliability patterns, observability best practices, and much more. Although you can build applications without knowing much of that, you will end up spending hours debugging and re-architecting them, learning hard lessons that you could have acquired in a much faster and less painful way.