<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<a href="https://blog.cleancoder.com/uncle-bob/2012/02/01/Service-Oriented-Agony.html" class="">https://blog.cleancoder.com/uncle-bob/2012/02/01/Service-Oriented-Agony.html</a>
<div class=""><br class="">
</div>
<div class="">voorbeelden binnen onze projecten:</div>
<div class="">
<ul class="MailOutline">
<li class="">DSI </li><li class="">GPBV</li><li class="">Erkenningen</li><li class="">DMVB</li><li class="">ETS of MDO</li><li class="">Seveso</li></ul>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><font size="4" class="">So what’s the solution? First of all, I question whether the system needed to be partitioned into services. Services are expensive and complicated, you should only create them if you absolutely need to. It’s always easier
to live in a single process. Remember Martin Fowler’s first law of distributed objects: <b class=""><i class=""><u class="">Don’t distribute your objects</u></i></b>.</font></div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">…</div>
<div class=""><br class="">
</div>
<div class=""><font size="4" class="">Like I said, I see this kind of partitioning a lot; and it always has the same outcome. It slows development because it smears features through many different layers. Many systems could be streamlined, and development made
much faster, if the system designers paid more attention to the Single Responsibility Principle.</font></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Mvg</div>
<div class="">Christophe</div>
</body>
</html>