Review of "Building Microservices" book by Sam Newman. Just a moment while we sign you in to your Goodreads account. The book covers interesting topics and some of the existing technologies around the use of microservices. February 20th 2015 The guidance contained in Building Microservices is valid but the execution feels sloppy and rushed. But developing these systems brings its own set of headaches. This conceptual book touches lots of aspects surrounding those little sisters of Service-oriented architectures (SOA): Starting from the basics, it covers topics like integration, splitting monoliths, deployment, testing, monitoring, security, system design and the role of architects, and scaling services.Microservices are a relatively new trend in computer science, coined around 2012. It covers a lot of ground, but nothing in depth. A book to read from beginning to end, but also one to consult. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. Good ideas and patterns for monolith split, too superficial on monitoring and a good start for developers who’s deciding if ms adoption is good.
Your recently viewed items and featured recommendations Still I found this book very good. Welcome back. Of course, you'll have to seek elsewhere to find those answers, but at least now you'll know what to look for.If you're new to microservices, this book is a decent intro, covering most of the major topics you need to be aware of. Be the first to ask a question about Building Microservices
Since my coworkers have mentioned hearing lots of hubbub about Microservices, I decided to run a little book club for my team. It still has a lot gold mines spread around the entire book. Microservices are implemented in Docker so I'll finally get to wrestle with that a bit too. A quick and information packed read.I've been seeing lots of talk about Microservices, and it's something I have virtually no experience with. Of course, you'll have to seek elsewhere to find those answers, but at least now you'll know what to look for.The Pragmatic Programmer of the microservices age. Not necessarily developers, designers and engineers.
I work in a firm which firmly believes that MicroServices are the way to move forward. Some of the topics discussed are: when microservice architecture should/shouldn't be used, splitting monolith applications, designing, deploying, testing, monitoring, and scaling microservices.I was somewhat skeptical about the book. This conceptual book touches lots of aspects surrounding those little sisters of Service-oriented architectures (SOA): Starting from the basics, it covers topics like integration, splitting monoliths, deployment, testing, monitoring, security, system design and the role of architects, and scaling services.Mixed feelings about this book. So expect the religious/consultant perspective.It's not only about microservices, it is a great book on modern distributed systems architecture In the end, you just feel confident to develop this way.If you have to read just one book about microservices, choose this. Its scope is very broad, but some may feel it doesn't hit enough depth on any one topic. The book does a good job exposing the ideas and good practices behind a migration to (micro)services. Sorry, this is not the book for ya.
First the architecture principles are hare, clearly stated and opiniated. It only covers the topics at a surface level (to be fair, it would've been a very long book if it went in-depth on each one), which is just enough to show you what questions you should be asking. Microservices aren't a silver bullet and perhaps you shouldn't event start with building one, monolithic codebases are fine for short or mid term runs, you can iterate fast, and refactoring and re … Unless they are looking for awareness. Job done. It only covers the topics at a surface level (to be fair, it would've been a very long book if it went in-depth on each one), which is just enough to show you what questions you should be asking.