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.
133 lines
5.9 KiB
133 lines
5.9 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">Microservice Patterns - Chris Richardson</h1> |
|
<span class="post-date"> |
|
2019-10-09 |
|
|
|
<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/spring/">#spring</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/java/">#java</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/stars-1/">#stars:1</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/published-2017/">#published:2017</a> |
|
|
|
</span> |
|
<p><a href="https://www.goodreads.com/book/show/34372564-microservice-patterns">GoodReads summary</a>: |
|
Microservice Patterns teaches enterprise developers and architects how to |
|
build applications with the microservice architecture. Rather than simply |
|
advocating for the use the microservice architecture, this clearly-written |
|
guide takes a balanced, pragmatic approach. You'll discover that the |
|
microservice architecture is not a silver bullet and has both benefits and |
|
drawbacks. Along the way, you'll learn a pattern language that will enable you |
|
to solve the issues that arise when using the microservice architecture. This |
|
book also teaches you how to refactor a monolithic application to a |
|
microservice architecture.</p> |
|
<span id="continue-reading"></span><div> |
|
★☆☆☆☆ |
|
</div> |
|
<p>I have a rule: The "badness" of a book is directly proportional to the number |
|
of "as follows" the author uses in it.</p> |
|
<p>And, oh boy, do they use "as follows" in this book (no, seriously).</p> |
|
<p>The first 1/4 of the book is pretty good, showing patterns and giving |
|
explanations about it. The rest of the book is strongly focused on external |
|
frameworks and libraries and has almost no patterns discussion at all -- for |
|
example, the second 1/4 is, basically, focused on the author's framework -- a |
|
Java framework. Also, the author seems strongly focused on Java code, even |
|
after explaining that a microservice fleet can be written in lots of different |
|
languages -- even listing some languages.</p> |
|
<p>There is a strong preference for Java and Spring on the book, to the point |
|
that, when discussing a point, it shows a Spring module with a huge |
|
explanation on what it does and another saying, simply, "another Java |
|
framework".</p> |
|
<p>The code examples are also bad. It seems the author decided to use IntelliJ as |
|
IDE and use its variable-name-generator (based on the class name) to create |
|
the variable names. Classes names are really long on Java and, using the IDE, |
|
the variables names <em>also</em> get really long, which by itself is not bad, |
|
but in a book, it means the code will get formatted like any text and, thus, |
|
get completely broken, and really hard to read.</p> |
|
<p>There are <em>lots</em> of images. And, as usual with a lot of images, 90% of |
|
them are completely irrelevant, adding absolutely nothing of whatever was |
|
described already.</p> |
|
<p>Those failures are extremely upsetting. You're getting a book about patterns |
|
and end up with lots of pages of discussion and code -- badly formatted code |
|
-- and very little pattern. Instead of explaining each pattern in depth, the |
|
author decided to skip the whole thing and just show you how to use some |
|
framework that already implements the pattern. That, by itself, isn't bad, but |
|
without understanding what the pattern is, and what it is good for, you won't |
|
know if it is a good idea to use it or not -- because patterns are ways to |
|
describe your solution, not "ready made" solutions.</p> |
|
<p>Honestly, I can't recommend this book for anyone that is starting their way |
|
into microservices.</p> |
|
|
|
</div> |
|
|
|
|
|
|
|
|
|
</div> |
|
|
|
</body> |
|
|
|
</html>
|
|
|