<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tags/Repository on Emad Alashi</title>
    <link>https://emadashi.com/tags/repository/</link>
    <description>Recent content in Tags/Repository on Emad Alashi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 09 Nov 2008 21:17:27 +0000</lastBuildDate>
    <atom:link href="https://emadashi.com/tags/repository/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Data Access Within Business Objects -Bunian Design-</title>
      <link>https://emadashi.com/2008/11/data-access-within-business-objects-bunian-design/</link>
      <pubDate>Sun, 09 Nov 2008 21:17:27 +0000</pubDate>
      <guid>https://emadashi.com/2008/11/data-access-within-business-objects-bunian-design/</guid>
      <description>&lt;p&gt;In a previous post I showed the general architecture of Bunian. I&amp;rsquo;d like, in this post, to touch on the Data Access part and how it interacts with the Business Objects.&lt;/p&gt;
&lt;p&gt;In traditional architectures there are 3 known layers: Data Access, Business, and Presentation. &lt;a href=&#34;http://en.wikipedia.org/wiki/Data_Transfer_Object&#34;&gt;DTO&amp;rsquo;s&lt;/a&gt; (Data Transfer Objects) are used to carry the data back and forth between the layers. Look to the following diagram:&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;DTO&#34; loading=&#34;lazy&#34; src=&#34;http://eashi.files.wordpress.com/2008/11/dto.jpg&#34;&gt;&lt;/p&gt;
&lt;p&gt;Bunian contributors seemed to have the same experience developing against such architecture, so we have decided to go with something different; smart Business Objects with more toward OOP.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
