<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Service granularity principle - Page 4 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Service_granularity_principle&amp;p=3">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Service_granularity_principle&amp;p=5">3.Next</a>
</p>
<p>design complexity but can reduce the number of calls required to complete a task.</p>

<p><big> Criteria </big></p>
<p>Due to the <a href="page.php?w=fallacies_of_distributed_computing">fallacies of distributed computing</a>, finding an adequate granularity is hard. There is no single simple answer but a number of criteria exist (see below). A primary goal of service modeling and granularity design is to achieve <a href="page.php?w=loose_coupling">loose coupling</a> and <a href="page.php?w=modularity">modularity</a>, which are two of the essential SOA</p><p>
<a accesskey="1" href="page.php?w=Service_granularity_principle&amp;p=3">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Service_granularity_principle&amp;p=5">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
