<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><channel rdf:about="https://www.bibsonomy.org/user/fmeyer/architecture"><title>BibSonomy bookmarks for /user/fmeyer/architecture</title><link>https://www.bibsonomy.org/user/fmeyer/architecture</link><description>BibSonomy RSS Feed for /user/fmeyer/architecture</description><items><rdf:Seq><rdf:li rdf:resource="http://cookiesareforclosers.com/blog/2008/06/linkedin-architecture"/><rdf:li rdf:resource="http://architects.dzone.com/news/common-rest-design-pattern"/><rdf:li rdf:resource="http://www.infoq.com/articles/rest-introduction"/><rdf:li rdf:resource="http://www.infoq.com/articles/louis-esb-topologies"/><rdf:li rdf:resource="http://www.infoq.com/interviews/jim-webber-qcon-london"/><rdf:li rdf:resource="http://www.mnot.net/blog/2007/04/29/squid"/><rdf:li rdf:resource="http://spreadsheets.google.com/pub?key=prCSPRhj1PCGuYZvjEITgXw&amp;gid=0"/><rdf:li rdf:resource="http://pilchardfriendly.blogspot.com/2007/02/what-colour-is-your-code.html"/><rdf:li rdf:resource="http://dev2dev.bea.com/pub/a/2006/11/effective-exceptions.html?page=1"/><rdf:li rdf:resource="http://www.infoq.com/minibooks/domain-driven-design-quickly"/><rdf:li rdf:resource="http://duncan-cragg.org/blog/post/right-way-to-do-ajax-is-declaratively/"/><rdf:li rdf:resource="http://www.datadirect.com/developer/jdbc/topics/jta/index.ssp"/><rdf:li rdf:resource="http://www.artima.com/weblogs/viewpost.jsp?thread=154933"/></rdf:Seq></items></channel><item rdf:about="http://cookiesareforclosers.com/blog/2008/06/linkedin-architecture"><title>Cookies are for Closers » LinkedIn Architecture</title><description>At JavaOne 2008, LinkedIn employees presented two sessions about the LinkedIn architecture. The slides are available online:</description><link>http://cookiesareforclosers.com/blog/2008/06/linkedin-architecture</link><dc:creator>fmeyer</dc:creator><dc:date>2008-06-06T16:57:15+02:00</dc:date><dc:subject>architecture linkedin performance scalability scaling </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;At JavaOne 2008, LinkedIn employees presented two sessions about the LinkedIn architecture. The slides are available online:&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/linkedin"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/performance"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/scalability"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/scaling"/></rdf:Bag></taxo:topics></item><item rdf:about="http://architects.dzone.com/news/common-rest-design-pattern"><title>Common REST Design Pattern | Architects Zone</title><description>Based on the same architectural pattern of the web, &#034;REST&#034; has a growing dominance of the SOA (Service Oriented Architecture) implementation these days. In this article, we will discuss some basic design principles of REST.</description><link>http://architects.dzone.com/news/common-rest-design-pattern</link><dc:creator>fmeyer</dc:creator><dc:date>2008-06-06T14:01:07+02:00</dc:date><dc:subject>architecture patterns rest </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Based on the same architectural pattern of the web, &amp;#034;REST&amp;#034; has a growing dominance of the SOA (Service Oriented Architecture) implementation these days. In this article, we will discuss some basic design principles of REST.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/patterns"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rest"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.infoq.com/articles/rest-introduction"><title>InfoQ: A Brief Introduction to REST</title><description>You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication:</description><link>http://www.infoq.com/articles/rest-introduction</link><dc:creator>fmeyer</dc:creator><dc:date>2008-05-28T18:20:11+02:00</dc:date><dc:subject>architecture design rest </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;You may or may not be aware that there is debate going on about the “right” way to implement heterogeneous application-to-application communication:&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/design"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rest"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.infoq.com/articles/louis-esb-topologies"><title>InfoQ: ESB Topology Alternatives</title><description>This article discusses several architecture and management topics for the two different approaches.</description><link>http://www.infoq.com/articles/louis-esb-topologies</link><dc:creator>fmeyer</dc:creator><dc:date>2008-05-27T15:56:40+02:00</dc:date><dc:subject>architecture articles esb soa </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;This article discusses several architecture and management topics for the two different approaches.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/articles"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/esb"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/soa"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.infoq.com/interviews/jim-webber-qcon-london"><title>InfoQ: Jim Webber on &#034;Guerilla SOA&#034;</title><description>In this interview, recorded at QCon London, Jim Webber, ThoughtWorks SOA practice leader talks to Stefan Tilkov about Guerilla SOA, Description Language (SSDL).</description><link>http://www.infoq.com/interviews/jim-webber-qcon-london</link><dc:creator>fmeyer</dc:creator><dc:date>2008-05-27T15:46:20+02:00</dc:date><dc:subject>architecture esb interview mest rest soa video webservices </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;In this interview, recorded at QCon London, Jim Webber, ThoughtWorks SOA practice leader talks to Stefan Tilkov about Guerilla SOA, Description Language (SSDL).&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/esb"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/interview"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/mest"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rest"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/soa"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/video"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/webservices"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.mnot.net/blog/2007/04/29/squid"><title>mnot’s Web log: Squid is My Service Bus</title><description>The QCon presentation (slides) was ostensibly about how we use HTTP for services within Yahoo’s Media Group.</description><link>http://www.mnot.net/blog/2007/04/29/squid</link><dc:creator>fmeyer</dc:creator><dc:date>2008-05-26T14:17:21+02:00</dc:date><dc:subject>apache architecture cache caching http proxy rest squid </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;The QCon presentation (slides) was ostensibly about how we use HTTP for services within Yahoo’s Media Group.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/apache"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/cache"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/caching"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/http"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/proxy"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rest"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/squid"/></rdf:Bag></taxo:topics></item><item rdf:about="http://spreadsheets.google.com/pub?key=prCSPRhj1PCGuYZvjEITgXw&amp;gid=0"><title>Google Docs &amp; Spreadsheets - My favorite SWE and Java Articles</title><description></description><link>http://spreadsheets.google.com/pub?key=prCSPRhj1PCGuYZvjEITgXw&amp;gid=0</link><dc:creator>fmeyer</dc:creator><dc:date>2007-08-25T17:39:45+02:00</dc:date><dc:subject>architecture design engineering j2ee java software </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2007-08-25T17:39:45+02:00&#034; href=&#034;http://spreadsheets.google.com/pub?key=prCSPRhj1PCGuYZvjEITgXw&amp;amp;gid=0&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://spreadsheets.google.com/pub?key=prCSPRhj1PCGuYZvjEITgXw&amp;amp;gid=0&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/design"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/engineering"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/j2ee"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/java"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/software"/></rdf:Bag></taxo:topics></item><item rdf:about="http://pilchardfriendly.blogspot.com/2007/02/what-colour-is-your-code.html"><title>Adventures in Geekland: What colour is your code?</title><description>Consider an [arbitrary] piece of code. It&#039;s indoors, it&#039;s well behaved, and you can be proud of it. What is it about that code that you like? Is it elegant? Is it clever? Does it enable something? How would you measure the value of code?</description><link>http://pilchardfriendly.blogspot.com/2007/02/what-colour-is-your-code.html</link><dc:creator>fmeyer</dc:creator><dc:date>2007-02-14T20:41:30+01:00</dc:date><dc:subject>architecture business development economics economy ideas information software toread </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Consider an [arbitrary] piece of code. It&amp;#039;s indoors, it&amp;#039;s well behaved, and you can be proud of it. What is it about that code that you like? Is it elegant? Is it clever? Does it enable something? How would you measure the value of code?&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/development"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/economics"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/economy"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ideas"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/information"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/software"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/toread"/></rdf:Bag></taxo:topics></item><item rdf:about="http://dev2dev.bea.com/pub/a/2006/11/effective-exceptions.html?page=1"><title>Effective Java Exceptions</title><description>One of the most important architectural decisions a Java developer can make is how to use the Java exception model. Java exceptions have been the subject of considerable debate in the community. Some have argued that checked exceptions in the Java languag</description><link>http://dev2dev.bea.com/pub/a/2006/11/effective-exceptions.html?page=1</link><dc:creator>fmeyer</dc:creator><dc:date>2007-01-20T21:10:49+01:00</dc:date><dc:subject>architecture design exception exceptions java patterns programming </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;One of the most important architectural decisions a Java developer can make is how to use the Java exception model. Java exceptions have been the subject of considerable debate in the community. Some have argued that checked exceptions in the Java languag&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/design"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/exception"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/exceptions"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/java"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/patterns"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/programming"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.infoq.com/minibooks/domain-driven-design-quickly"><title>InfoQ: Domain Driven Design Quickly</title><description>The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domai</description><link>http://www.infoq.com/minibooks/domain-driven-design-quickly</link><dc:creator>fmeyer</dc:creator><dc:date>2006-12-09T18:51:18+01:00</dc:date><dc:subject>DDD architecture book design development domain driven free pdf </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domai&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/DDD"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/book"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/design"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/development"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/domain"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/driven"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/free"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/pdf"/></rdf:Bag></taxo:topics></item><item rdf:about="http://duncan-cragg.org/blog/post/right-way-to-do-ajax-is-declaratively/"><title>The Right Way to do Ajax is Declaratively | What Not How | http://duncan-cragg.org/blog/</title><description>Don&#039;t write your interactive Web application in custom Javascript! The Web&#039;s Declarative nature needn&#039;t be broken just because you want two-way dynamic data instead of one-way documents on your site.</description><link>http://duncan-cragg.org/blog/post/right-way-to-do-ajax-is-declaratively/</link><dc:creator>fmeyer</dc:creator><dc:date>2006-11-13T16:40:25+01:00</dc:date><dc:subject>ajax architecture declarative development javascript microformats web2.0 </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Don&amp;#039;t write your interactive Web application in custom Javascript! The Web&amp;#039;s Declarative nature needn&amp;#039;t be broken just because you want two-way dynamic data instead of one-way documents on your site.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ajax"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/declarative"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/development"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/javascript"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/microformats"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/web2.0"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.datadirect.com/developer/jdbc/topics/jta/index.ssp"><title>Understanding JTA—the Java Transaction API: JDBC Topics: JDBC: Developer: Home</title><description>The Java® Transaction API (JTA) allows applications to perform distributed transactions, that is, transactions that access and update data on two or more networked computer resources. The JTA specifies standard Java interfaces between a transaction manag</description><link>http://www.datadirect.com/developer/jdbc/topics/jta/index.ssp</link><dc:creator>fmeyer</dc:creator><dc:date>2006-09-15T16:19:12+02:00</dc:date><dc:subject>JTA architecture java transactions xa </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;The Java® Transaction API (JTA) allows applications to perform distributed transactions, that is, transactions that access and update data on two or more networked computer resources. The JTA specifies standard Java interfaces between a transaction manag&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/JTA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/java"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/transactions"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/xa"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.artima.com/weblogs/viewpost.jsp?thread=154933"><title>Software Architecture is Leadership</title><description>Summary A software architecture should not only explain how things are done in a software project, it should guide the team in that direction.</description><link>http://www.artima.com/weblogs/viewpost.jsp?thread=154933</link><dc:creator>fmeyer</dc:creator><dc:date>2006-04-05T03:54:49+02:00</dc:date><dc:subject>architecture leadership management software </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Summary A software architecture should not only explain how things are done in a software project, it should guide the team in that direction.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/leadership"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/management"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/software"/></rdf:Bag></taxo:topics></item></rdf:RDF>