You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
125 lines
5.6 KiB
125 lines
5.6 KiB
<!DOCTYPE html> |
|
<html lang="en"> |
|
<head> |
|
<meta http-equiv="X-UA-Compatible" content="IE=edge"> |
|
<meta http-equiv="content-type" content="text/html; charset=utf-8"> |
|
|
|
<!-- Enable responsiveness on mobile devices--> |
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape--> |
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover"> |
|
|
|
<title>Julio Biason .Me 4.3</title> |
|
|
|
<!-- CSS --> |
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print"> |
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css"> |
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css"> |
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface"> |
|
|
|
|
|
|
|
|
|
|
|
</head> |
|
|
|
<body class=" "> |
|
|
|
<div class="sidebar"> |
|
<div class="container sidebar-sticky"> |
|
<div class="sidebar-about"> |
|
|
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a> |
|
|
|
<p class="lead">Old school dev living in a 2.0 dev world</p> |
|
|
|
|
|
</div> |
|
|
|
<ul class="sidebar-nav"> |
|
|
|
|
|
<li class="sidebar-nav-item"><a href="/">English</a></li> |
|
|
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li> |
|
|
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li> |
|
|
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li> |
|
|
|
|
|
</ul> |
|
</div> |
|
</div> |
|
|
|
|
|
<div class="content container"> |
|
|
|
<div class="post"> |
|
<h1 class="post-title">Microservices In Action - Morgan Bruce</h1> |
|
<span class="post-date"> |
|
2019-08-13 |
|
|
|
<a href="https://blog.juliobiason.me/tags/books/">#books</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/reviews/">#reviews</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/microservices/">#microservices</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/morgan-bruce/">#morgan bruce</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/it/">#it</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/stars-2/">#stars:2</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/published-2017/">#published:2017</a> |
|
|
|
</span> |
|
<p><a href="https://www.goodreads.com/book/show/36579817-microservices-in-action">GoodReads summary</a>: |
|
Microservices in Action is a practical book about building and deploying |
|
microservice-based applications. Written for developers and architects with a |
|
solid grasp of service-oriented development, it tackles the challenge of |
|
putting microservices into production. You'll begin with an in-depth overview |
|
of microservice design principles, building on your knowledge of traditional |
|
systems. Then, you'll start creating a reliable road to production. You'll |
|
explore examples using Kubernetes, Docker, and Google Container Engine as you |
|
learn to build clusters and maintain them after deployment. Throughout this |
|
rich, experience-driven book, you'll move through real-world use cases |
|
including a continuous delivery pipeline, production monitoring, and practical |
|
techniques for scaling and maintaining a healthy system.</p> |
|
<span id="continue-reading"></span><div> |
|
★★☆☆☆ |
|
</div> |
|
<p>For an "In Action" title, there is very little "Action" going on. Not that the |
|
book lacks information: There is plenty of theoretical information, although a |
|
lot is hidden in "cohesive" adjectives: "If you do this, the service will not |
|
be cohesive", "doing so will make it more cohesive"... and what the author |
|
means by "cohesive" is never explained -- I'd ask the author to replace every |
|
reference to cohesive with a proper explanation.</p> |
|
<p>Also, there are a lot of images. Not that images by themselves is bad, but when |
|
they are used for the obvious, it really irks me -- specially 'cause I read |
|
those books on a "black background with white letters" and images do not fit |
|
that properly, using a white background that usually just hurts my eyes. And by |
|
"used for the obvious", there are images follow the description of "A and B |
|
communicate with C" and a large image showing <code>A --> C <-- B</code>; was that really |
|
necessary?</p> |
|
<p>The intro says the code is in Python, and that was something that I'd really |
|
like to see. There is very little code in this book and the parts shown are |
|
basically "look at this library" instead of focusing on what it really does; a |
|
library for retrying is nice and all, but would it be so hard to write the |
|
code, even if that code would be somewhat longer, to show the point you're |
|
trying to make instead of being just an example of a library?</p> |
|
<p>Speaking of code, there is also a long discussion about deploying |
|
microservices, which is a good thing, but the author decided that it would use |
|
Google Cloud Platform and every single explanation focuses more on how to |
|
deploy on GCP instead of actually discussing deployment. </p> |
|
|
|
</div> |
|
|
|
|
|
|
|
|
|
</div> |
|
|
|
</body> |
|
|
|
</html>
|
|
|