<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (DennisLaumen)</title>
    <link>https://pinboard.in/u:DennisLaumen/public/</link>
    <description>recent bookmarks from DennisLaumen</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.aosabook.org/en/"/>
	<rdf:li rdf:resource="http://alistair.cockburn.us/Walking+skeleton"/>
	<rdf:li rdf:resource="http://www.udidahan.com/2009/12/09/clarified-cqrs/"/>
	<rdf:li rdf:resource="http://wiki.sharparchitecture.net/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.aosabook.org/en/">
    <title>The Architecture of Open Source Applications</title>
    <dc:date>2014-07-12T20:50:49+00:00</dc:date>
    <link>http://www.aosabook.org/en/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.

Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think.

If you are a junior developer, and want to learn how your more experienced colleagues think, these books are the place to start. If you are an intermediate or senior developer, and want to see how your peers have solv]]></description>
<dc:subject>books softwarearchitecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:62d30e33978d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwarearchitecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistair.cockburn.us/Walking+skeleton">
    <title>Walking skeleton</title>
    <dc:date>2012-09-16T16:27:34+00:00</dc:date>
    <link>http://alistair.cockburn.us/Walking+skeleton</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[A Walking Skeleton is a tiny implementation of the system that performs a small end-to-end function. It need not use the final architecture, but it should link together the main architectural components. The architecture and the functionality can then evolve in parallel.
]]></description>
<dc:subject>softwarearchitecture alistaircockburn</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:0c4bb34fdb09/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwarearchitecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:alistaircockburn"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.udidahan.com/2009/12/09/clarified-cqrs/">
    <title>Clarified CQRS</title>
    <dc:date>2010-12-22T13:06:08+00:00</dc:date>
    <link>http://www.udidahan.com/2009/12/09/clarified-cqrs/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[After listening how the community has interpreted Command-Query Responsibility Segregation I think that the time has come for some clarification. Some have been tying it together to Event Sourcing. Most have been overlaying their previous layered architecture assumptions on it. Here I hope to identify CQRS itself, and describe in which places it can connect to other patterns.]]></description>
<dc:subject>softwareengineering softwarearchitecture cqrs udidahan eventsourcing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:9505e5f932e4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwarearchitecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:cqrs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:udidahan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:eventsourcing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.sharparchitecture.net/">
    <title>Sh#rp Architecture</title>
    <dc:date>2010-12-20T12:50:42+00:00</dc:date>
    <link>http://wiki.sharparchitecture.net/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Pronounced "Sharp Architecture," this is a solid architectural foundation for rapidly building maintainable web applications leveraging the ASP.NET MVC framework with NHibernate. The primary advantage to be sought in using any architectural framework is to decrease the code one has to write while increasing the quality of the end product. A framework should enable developers to spend little time on infrastructure details while allowing them to focus their attentions on the domain and user experience. Accordingly, S#arp Architecture adheres to the following key principles:

- Focused on Domain Driven Design
- Loosely coupled
- Preconfigured Infrastructure
- Open Ended Presentation

The overall goal of this is to allow developers to worry less about application "plumbing" and to spend most of their time on adding value for the client by focusing on the business logic and developing a rich user experience.]]></description>
<dc:subject>softwarearchitecture softwaredevelopment domaindrivendesign .net nhibernate asp.netmvc</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:d2652b130f80/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwarearchitecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwaredevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:domaindrivendesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:.net"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:nhibernate"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:asp.netmvc"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>