I assume that this book is for beginners and also for people who are already using microservices.
Does the book help in understanding the differences between microservices and webservices, where to use them where not? or suggest design guidelines etc?
I have always seen webservices and micros as different points on the same continuum. Microservices suffers from the same problems that we used to face when we tried to fix the canonical view or to fix the scope of the webservice. Becuase we can make it very granular, so that the microservices are independent, but then we increase the network traffic and surely the operational cost, supplier costs.
The service discovery that was cited in chapter 2 is like the UDDI purported by IBM which did not take much flight, again thought of previously.
Yes I discuss design questions quite a lot in the book. It's not really a coding book (only chapter 9 has code), more of an architecture guide.
Web services can be implemented with microservices certainly, but they are different things. A web service is an API abstraction offered over HTTP - it's implementation should be hidden.
It could be a monolith, or microservices, behind the HTTP interface.
Microservices are not necessarily little web servers either - this is a common implementation, but not essential. For example, you could use a message bus instead to communicate between services.
In the book I introduce the design concept of "transport independence" which makes this explicit - microservices send and receive messages, but how that happens should not concern the service.