{"id":992,"date":"2007-04-05T13:06:12","date_gmt":"2007-04-05T13:06:12","guid":{"rendered":"http:\/\/www.redmonk.com\/jgovernor\/2007\/04\/05\/why-applications-are-like-fish-and-data-is-like-wine\/"},"modified":"2007-04-05T13:06:12","modified_gmt":"2007-04-05T13:06:12","slug":"why-applications-are-like-fish-and-data-is-like-wine","status":"publish","type":"post","link":"https:\/\/redmonk.com\/jgovernor\/why-applications-are-like-fish-and-data-is-like-wine\/","title":{"rendered":"Why Applications Are Like Fish and Data is Like Wine"},"content":{"rendered":"<p><img decoding=\"async\" src=\"http:\/\/farm1.static.flickr.com\/188\/432286274_eb853a784e.jpg?v=0\" alt=\"wine rack\" \/><\/p>\n<p>Only one improves with age. With apologies to the originator of the phrase &#8211; &#8220;Hardware is like fish, operating systems are like wine.&#8221;<\/p>\n<p>What am I talking about? Processes change, and need to change. Baking data into the application is a bad idea because the data can&#8217;t then be extended in useful, and &#8220;unexpected ways&#8221;. But not expecting corporate data to be used in new ways is kind of like not expecting the Spanish Inquisition. But&#8230; &#8220;NOBODY expects the Spanish Inquisition! Amongst our weaponry are such diverse elements as: fear, surprise, ruthless efficiency, an almost fanatical devotion to the Pope.&#8221; (sounds like Enterprise Architecture to me).<\/p>\n<p>I didn&#8217;t <a href=\"http:\/\/www.enterprisey.co.uk\/blog\/2006\/10\/24\/data-is-the-intel-inside\/\">go quiet Dennis<\/a>, I just didn&#8217;t post this. So if enterprise apps are so cool- why are SAP, IBM and Oracle all competing in the Master Data Management Space? If enterprise apps cut the mustard why is ETL and datawarehousing still a strong market. If the app matters more than the tax algorithms why is Oracle bothering to sue SAP?<\/p>\n<p>I actually really don&#8217;t like the bracketing of data extensibility as The Intel Inside. In fact I hate that way of articulating it. Because to my mind Intel may be a standard, but its not an open standard (well it wasn&#8217;t until AMD started to really nail it).<\/p>\n<p>Of course process matters but its better to crucial to invest in having the right data. Arguably the pitch SAP traditionally made was not that it would sell you a suite of apps, but rather than it would bring all your corporate data into one place so that you can make business decisions based on facts rather than suppositions. SAP&#8217;s story today still talks clearly to this corporate data standardisation.<\/p>\n<p>Information wants to be free. the Intel Inside slogan came from a monolith\/island era. That&#8217;s not where we&#8217;re going next.<\/p>\n<p>In this industry we tend to focus on the need to separate data from presentation, but of course we also try and enforce a separation beween data and business logic. Why? Because business logic quickly begins to smell. From a pace layering perspective.. oh wait, y&#8217;all probably don&#8217;t know what pace layering is. Its this cool idea from Stewart Brand, explained here (by <a href=\"http:\/\/www.boxesandarrows.com\/person\/donnamaurer\">Donna Maurer<\/a>)<\/p>\n<blockquote><p>&#8220;Complex systems can be decomposed into multiple layers, where the layers change at different rates. The \u201cfast layers\u201d learn, absorb shocks and get attention; the \u201cslow layers\u201d remember, constrain and have power. One of the implications of this model is that information architects can do what they have always done\u2013slow, deep, rich work; while tagging can spin madly on the surface. If it is worth keeping, it will seep down into the lower layers.&#8221; <\/p><\/blockquote>\n<p>Which talks pretty well to my point. Has anyone formally mapped Model-View-Controller to pace layering? I doubt it. But if we look at business architectures data has the longest shelf life, followed by business logic, followed by presentation. Sometimes the data stays the same but the data model changes, another layer. Presentation goes off even faster than fish [ed: what <em>does<\/em> go off faster than fish, or is this metaphor b0rked? Why do shops keep investing in mainframes? Because they are investing in data. Why do people keep buying apps? Because their old ones went off.<\/p>\n<p>Just to abuse the metaphor a little bit more there are some interesting things to note about wine. Not all wine is designed to be kept. Not all data increases in value over time. If organisations spent more time working out what wine was worth keeping, and which had turned to vinegar, they would be a lot better off. Retain the data that has value. In some applications- market risk for example-the only reason to keep historical data is regulatory requirements. Operational risk on the other hand needs to more cognizant of trending. For market data risk <a href=\"http:\/\/www.stormhoek.com\/archives\/2005\/07\/wine_blogging_a_1.php\">freshness matters<\/a>.<\/p>\n<p>Dennis says:<\/p>\n<blockquote><p>&#8220;To me, data is valuable for understanding what is going on inside a process. The data may suggest an alternative course of action. But that in itself implies the application of process steps and will have been the result of pre-presentation filtering and refining, via business processes.&#8221;<\/p><\/blockquote>\n<p>. The process provides a context for the data, sure, but could the process or application be different? Regardless of whether or not corporate data has a life outside the process, which of course i think it does, it would still pay organisations to really think through their data, and what its for. We don&#8217;t want it all in the cellar, after all. Sometimes you need a drink. Anyway- what do you all think?<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/farm1.static.flickr.com\/54\/191432293_7104ef5f64.jpg?v=0\" alt=\"fish\" \/><\/p>\n<p>disclaimers: IBM is a client, SAP soon will be, and Oracle we&#8217;re working on<br \/>\ncredits: wine picture courtesy of <a href=\"http:\/\/flickr.com\/photos\/avlxyz\/\">avixyz<\/a> on Flickr. fish courtesy of <a href=\"http:\/\/flickr.com\/photos\/39151655@N00\/191432293\/\">midquel<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Only one improves with age. With apologies to the originator of the phrase &#8211; &#8220;Hardware is like fish, operating systems are like wine.&#8221; What am I talking about? Processes change, and need to change. Baking data into the application is a bad idea because the data can&#8217;t then be extended in useful, and &#8220;unexpected ways&#8221;.<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[1],"tags":[],"class_list":["post-992","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p9wfjh-g0","_links":{"self":[{"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/posts\/992","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/comments?post=992"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/posts\/992\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/media?parent=992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/categories?post=992"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/jgovernor\/wp-json\/wp\/v2\/tags?post=992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}