<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ToddFredrich.com</title>
	<atom:link href="http://toddfredrich.com/feed" rel="self" type="application/rss+xml" />
	<link>https://toddfredrich.com/</link>
	<description>RESTful/Platform APIs and Examples, Tutorials and the Software Craft. Mostly...</description>
	<lastBuildDate>Thu, 09 Oct 2014 14:59:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
<site xmlns="com-wordpress:feed-additions:1">44749925</site>	<item>
		<title>&#8220;Experience API&#8221; defines Every API</title>
		<link>https://toddfredrich.com/experience-api-defines-every-api.html</link>
					<comments>https://toddfredrich.com/experience-api-defines-every-api.html#comments</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Tue, 14 Oct 2014 16:21:18 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[API Strategy]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=205</guid>

					<description><![CDATA[<p>Daniel Jacobson, Director of Engineering &#8211; Netflix API, uses some terms in his post, The future of API design: The orchestration layer, that are making things difficult for those of us trying to communicate in the API space.  Specifically,  the two terms, &#8220;API Orchestration Layer&#8221; and &#8220;Experience API.&#8221;  These are neither accurate nor meaningful.  Let me explain&#8230; &#8230; <a href="https://toddfredrich.com/experience-api-defines-every-api.html" class="more-link">Continue reading<span class="screen-reader-text"> "&#8220;Experience API&#8221; defines Every API"</span></a></p>
<p>The post <a href="https://toddfredrich.com/experience-api-defines-every-api.html">&#8220;Experience API&#8221; defines Every API</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/experience-api-defines-every-api.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">205</post-id>	</item>
		<item>
		<title>RestExpress API Application Layers</title>
		<link>https://toddfredrich.com/restexpress-api-application-layers.html</link>
					<comments>https://toddfredrich.com/restexpress-api-application-layers.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Thu, 09 Oct 2014 14:50:14 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[RestExpress]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Video]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=228</guid>

					<description><![CDATA[<p>Here&#8217;s a quickie video describing the application layers of a RestExpress application when one of the Maven Archetypes is used to create a new RestExpress project. http://youtu.be/ZFqjvNiB-hY To summarize: Visibility or &#8220;awareness&#8221; goes down. Meaning that a layer can call (or know about) the layer immediately below it, but an application layer cannot call the layer &#8230; <a href="https://toddfredrich.com/restexpress-api-application-layers.html" class="more-link">Continue reading<span class="screen-reader-text"> "RestExpress API Application Layers"</span></a></p>
<p>The post <a href="https://toddfredrich.com/restexpress-api-application-layers.html">RestExpress API Application Layers</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/restexpress-api-application-layers.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">228</post-id>	</item>
		<item>
		<title>The Commoditization of the User Interface</title>
		<link>https://toddfredrich.com/commoditization-of-the-user-interface.html</link>
					<comments>https://toddfredrich.com/commoditization-of-the-user-interface.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Tue, 30 Sep 2014 22:28:18 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[HATEOAS]]></category>
		<category><![CDATA[Media Types]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=184</guid>

					<description><![CDATA[<p>The public face of a business system is its user interface (UI)&#8211;the part the end-user sees. Businesses often think in terms of user interface design. Many times they also consider it the facet that gives them an edge in their market (the &#8220;killer app&#8221;).  Being overly concerned with the UI first, focusing on what the web &#8230; <a href="https://toddfredrich.com/commoditization-of-the-user-interface.html" class="more-link">Continue reading<span class="screen-reader-text"> "The Commoditization of the User Interface"</span></a></p>
<p>The post <a href="https://toddfredrich.com/commoditization-of-the-user-interface.html">The Commoditization of the User Interface</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/commoditization-of-the-user-interface.html/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">184</post-id>	</item>
		<item>
		<title>Building a 1&#215;12 Guitar Speaker Cabinet</title>
		<link>https://toddfredrich.com/building-a-1x12-guitar-speaker-cabinet.html</link>
					<comments>https://toddfredrich.com/building-a-1x12-guitar-speaker-cabinet.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Fri, 06 Sep 2013 00:09:11 +0000</pubDate>
				<category><![CDATA[Guitar]]></category>
		<category><![CDATA[Music]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=148</guid>

					<description><![CDATA[<p>As an amateur electric guitarist, one eventually begins to seek a better sound. Tube amps are supposed to be the bomb, right? Well, some time ago, I bought a Blackheart Little Giant 5 amp, used.  It&#8217;s a single-channel 5W, single-ended, class A amp powered by an EL84 and voiced through a 12AX7 preamp tube.  Not &#8230; <a href="https://toddfredrich.com/building-a-1x12-guitar-speaker-cabinet.html" class="more-link">Continue reading<span class="screen-reader-text"> "Building a 1&#215;12 Guitar Speaker Cabinet"</span></a></p>
<p>The post <a href="https://toddfredrich.com/building-a-1x12-guitar-speaker-cabinet.html">Building a 1&#215;12 Guitar Speaker Cabinet</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/building-a-1x12-guitar-speaker-cabinet.html/feed</wfw:commentRss>
			<slash:comments>23</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">148</post-id>	</item>
		<item>
		<title>RestExpress Still Top Performing MongoDB REST Framework</title>
		<link>https://toddfredrich.com/restexpress-top-performing-mongodb-rest-framework.html</link>
					<comments>https://toddfredrich.com/restexpress-top-performing-mongodb-rest-framework.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Thu, 22 Aug 2013 15:55:03 +0000</pubDate>
				<category><![CDATA[RestExpress]]></category>
		<category><![CDATA[mongodb]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[restexpress]]></category>
		<category><![CDATA[restful services]]></category>
		<category><![CDATA[web services]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=137</guid>

					<description><![CDATA[<p>Round six of the TechEmpower.com Web Framework benchmarks were published on July 2, 2013, which show RestExpress 0.9.2 as still the best performing REST Framework against MongoDB (2.2.4) for single-query, CRUD-style operations.  At 63,209 responses per second on an i7-2600K (with 8GB memory) and 7,547 responses per second on an AWS EC2 m1.large instance, it ranked 10th &#8230; <a href="https://toddfredrich.com/restexpress-top-performing-mongodb-rest-framework.html" class="more-link">Continue reading<span class="screen-reader-text"> "RestExpress Still Top Performing MongoDB REST Framework"</span></a></p>
<p>The post <a href="https://toddfredrich.com/restexpress-top-performing-mongodb-rest-framework.html">RestExpress Still Top Performing MongoDB REST Framework</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/restexpress-top-performing-mongodb-rest-framework.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">137</post-id>	</item>
		<item>
		<title>Idempotency in REST APIs</title>
		<link>https://toddfredrich.com/idempotency-in-rest-apis.html</link>
					<comments>https://toddfredrich.com/idempotency-in-rest-apis.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Tue, 20 Aug 2013 18:26:54 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[Intro to REST]]></category>
		<category><![CDATA[REST Tips]]></category>
		<category><![CDATA[idempotence]]></category>
		<category><![CDATA[idempotency]]></category>
		<category><![CDATA[idempotent]]></category>
		<category><![CDATA[rest]]></category>
		<category><![CDATA[rest api]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=135</guid>

					<description><![CDATA[<p>Idempotence is sometimes a confusing concept, especially when you try to understand the academic definition. However, understanding what makes a REST API operation idempotent is simple with the concept introduced in this short, somewhat humorous look at Idempotency in Cows &#38; REST APIs&#8230; &#160;</p>
<p>The post <a href="https://toddfredrich.com/idempotency-in-rest-apis.html">Idempotency in REST APIs</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/idempotency-in-rest-apis.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">135</post-id>	</item>
		<item>
		<title>What to Use as Identifiers (IDs) in REST APIs</title>
		<link>https://toddfredrich.com/ids-in-rest-api.html</link>
					<comments>https://toddfredrich.com/ids-in-rest-api.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Wed, 14 Aug 2013 20:18:20 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[REST Tips]]></category>
		<category><![CDATA[RestExpress]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=131</guid>

					<description><![CDATA[<p>TIP: Publicly exposed identifiers (IDs), such as those exposed in your RESTful URLs, should not expose underlying technology. And in most cases, should not contain business meaning. For a long time it&#8217;s been good practice to ensure that primary keys in your database tables do not contain business semantics so that it doesn&#8217;t change when the &#8230; <a href="https://toddfredrich.com/ids-in-rest-api.html" class="more-link">Continue reading<span class="screen-reader-text"> "What to Use as Identifiers (IDs) in REST APIs"</span></a></p>
<p>The post <a href="https://toddfredrich.com/ids-in-rest-api.html">What to Use as Identifiers (IDs) in REST APIs</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/ids-in-rest-api.html/feed</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">131</post-id>	</item>
		<item>
		<title>REST API Versioning: Good, Bad or Ugly?</title>
		<link>https://toddfredrich.com/rest-api-versioning-good-bad-or-ugly.html</link>
					<comments>https://toddfredrich.com/rest-api-versioning-good-bad-or-ugly.html#comments</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Wed, 31 Jul 2013 19:03:56 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[REST Tips]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=112</guid>

					<description><![CDATA[<p>The Prelims There are a lot of efforts and words spent around making sure we account for the changes of business in our RESTful services.  One of those &#8216;contingencies&#8217; we often account for is versioning of resources and/or representations.  Historically, versioning recommendations were often the following: Place a version number, something like &#8216;v1&#8217;, in the &#8230; <a href="https://toddfredrich.com/rest-api-versioning-good-bad-or-ugly.html" class="more-link">Continue reading<span class="screen-reader-text"> "REST API Versioning: Good, Bad or Ugly?"</span></a></p>
<p>The post <a href="https://toddfredrich.com/rest-api-versioning-good-bad-or-ugly.html">REST API Versioning: Good, Bad or Ugly?</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/rest-api-versioning-good-bad-or-ugly.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">112</post-id>	</item>
		<item>
		<title>Instant REST Services with RESTExpress Q&#038;A</title>
		<link>https://toddfredrich.com/instant-rest-services-with-restexpress-qa.html</link>
					<comments>https://toddfredrich.com/instant-rest-services-with-restexpress-qa.html#respond</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Wed, 09 Jan 2013 16:25:55 +0000</pubDate>
				<category><![CDATA[Intro to REST]]></category>
		<category><![CDATA[REST Constraints]]></category>
		<category><![CDATA[REST Tips]]></category>
		<category><![CDATA[RestExpress]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[mongodb]]></category>
		<category><![CDATA[q&a]]></category>
		<category><![CDATA[restexpress]]></category>
		<category><![CDATA[restful services]]></category>
		<category><![CDATA[youtube video]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=99</guid>

					<description><![CDATA[<p>This is a follow-on to my last two posts, Introduction to REST (Revisited) and RESTExpress Overview and Tutorial, with this short video being the Q&#38;A after the presentation.  In it, the video talks about authentication, authorization, and some of the RESTExpress features around sorting, filtering and performance.  It&#8217;s a quickie, but it&#8217;s always nice to &#8230; <a href="https://toddfredrich.com/instant-rest-services-with-restexpress-qa.html" class="more-link">Continue reading<span class="screen-reader-text"> "Instant REST Services with RESTExpress Q&#38;A"</span></a></p>
<p>The post <a href="https://toddfredrich.com/instant-rest-services-with-restexpress-qa.html">Instant REST Services with RESTExpress Q&amp;A</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/instant-rest-services-with-restexpress-qa.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">99</post-id>	</item>
		<item>
		<title>RESTExpress Overview and Tutorial</title>
		<link>https://toddfredrich.com/restexpress-overview-and-tutorial.html</link>
					<comments>https://toddfredrich.com/restexpress-overview-and-tutorial.html#respond</comments>
		
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Mon, 07 Jan 2013 16:56:55 +0000</pubDate>
				<category><![CDATA[API Design]]></category>
		<category><![CDATA[Intro to REST]]></category>
		<category><![CDATA[REST Tips]]></category>
		<category><![CDATA[RestExpress]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[rest]]></category>
		<category><![CDATA[restexpress]]></category>
		<category><![CDATA[restful services]]></category>
		<category><![CDATA[software tutorial]]></category>
		<category><![CDATA[web services]]></category>
		<category><![CDATA[youtube video]]></category>
		<guid isPermaLink="false">http://toddfredrich.com/?p=92</guid>

					<description><![CDATA[<p>In my last post, Intro to REST (Revisited), as well as discussing the six constraints of the REST architectural style, the video discussed the background for the Java Rest Service Framework, RESTExpress and introduces a sample project.  The video below is part two of the presentation, where we dive in and create a real, working &#8230; <a href="https://toddfredrich.com/restexpress-overview-and-tutorial.html" class="more-link">Continue reading<span class="screen-reader-text"> "RESTExpress Overview and Tutorial"</span></a></p>
<p>The post <a href="https://toddfredrich.com/restexpress-overview-and-tutorial.html">RESTExpress Overview and Tutorial</a> appeared first on <a href="https://toddfredrich.com">ToddFredrich.com</a>.</p>
]]></description>
		
					<wfw:commentRss>https://toddfredrich.com/restexpress-overview-and-tutorial.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">92</post-id>	</item>
	</channel>
</rss>
