{"id":2785,"date":"2019-09-03T10:05:19","date_gmt":"2019-09-03T14:05:19","guid":{"rendered":"http:\/\/www.soul-repairs.com\/blog\/?p=2785"},"modified":"2019-09-02T00:50:11","modified_gmt":"2019-09-02T04:50:11","slug":"applications-are-gold","status":"publish","type":"post","link":"https:\/\/soul-repairs.com\/blog\/2019\/09\/03\/applications-are-gold\/","title":{"rendered":"Applications are Gold"},"content":{"rendered":"

We’ve talked previously about how developers drive organizational success<\/a>: they deliver the applications by which companies deliver their competitive advantages. Because<\/em> they are a way for companies to deliver products to customers, those delivered applications are critically valuable. Application development is a lot like extracting gold<\/a> – it creates value<\/em> out of raw resources<\/em>.<\/p>\n

Application development is a lot like extracting gold – it creates value<\/strong> out of raw resources<\/strong>.<\/p><\/blockquote>\n

Gold,\u00a0wealth<\/em>, needs to have some amount of protection.<\/p>\n

<\/p>\n

Protection<\/h2>\n

Applications are made up of two kinds of assets: the code<\/strong> and the architecture<\/strong>.<\/p>\n

The Code<\/h3>\n

Protecting the value inherent in code<\/strong>, or what<\/em> the application does, is pretty simple (…but not always easy!). You want to house it in a standardized source control management (SCM) tool, with versioning, and you want to regularly make sure that it can build<\/em> (be turned from raw source code into something that can actually\u00a0run<\/em>\u00a0on a platform). SCM with versioning matters so that a) you don’t lose<\/em> your source code (a horrible alternative to this would be the source code just hanging out on someone’s computer…) and b) if you make a change you didn’t mean to make, you can go back to an older version. SCM means that the code gets to continue to\u00a0exist<\/em> – it’s the most fundamental of protections. The ability to build matters in part because it’s the only way to resolve a code vulnerability in an included library – basically, if you need<\/em> to release a change to an application for some reason, building it is the first step after the code is changed, and the technical debt behind not building for a long time means that this can be a major bottleneck.<\/p>\n

Open source-based products are the best plan for vital enterprise tools, for reasons we’ll explain in another post – but for a SCM, that means using something Git-based<\/a>. The ability to build whenever you need to – or, said another way, releasing regularly and frequently –<\/strong> is solved via continuous delivery<\/a>. Or…continuous delivery\u00a0ish<\/em>. Just…release more than never, okay?<\/p>\n

The Architecture<\/h3>\n

Protecting the value of architecture<\/strong>, or how<\/em> the application does what it does, both now and in the future, is…less simple. The best thing to keep in mind is to make sure that the application can run where<\/em> you want it to run, how<\/em> you want it to run. Scalability (how well it responds to growth, usually referring to the number of users, the amount of data it interacts with, or the processing it has to do), cost (how much the platform costs to run the application), portability (the ability to run on more than one platform), and performance (how well it responds) are all important here. The best choice we (IT as a whole) know of today for scalability, portability, and<\/em> performance (…and usually cost) is container technology<\/a>\u00a0 Serverless technology<\/a> is more scalable, and may be cheaper, but it’s still in its infancy and isn’t something most enterprises can support.<\/p>\n

The best thing to keep in mind is to make sure the application can run where<\/strong> you want it to run, how<\/strong> you want it to run. The best choice we (IT as a whole) know of today to accomplish this is container technology<\/a>.<\/p><\/blockquote>\n

Platforms<\/h3>\n

If applications are gold, then platforms, or where you run<\/em> those applications, end up a lot like banks…if banks took gold directly. You need somewhere to store your gold, ideally where it’s still accessible and usable<\/em> – because running around with bars of gold in your pocket isn’t entirely practical. Those suckers are heavy<\/em>. Ideally, though, if at any point you need or want to move your gold to a different bank, you’d be able to do that without paying a hefty penalty. In IT, that penalty is usually\u00a0time<\/em> – time to refactor an application to successfully run on a different<\/strong> platform.<\/p>\n

Imagine if the bank only allowed you to spend $50 worth of gold every day, despite having several thousand dollars’ worth of gold in there. If your gold is stuck in that one bank, with hefty penalties to move it, then it’s really<\/em> only as usable as the features and rules of that bank.<\/p>\n

Containers<\/h2>\n

Containers deliver on scalability and portability, better than anything else currently out there. You can run a container built on standardized, open technology (Docker<\/a>, CRI-O<\/a>) on almost any container platform these days – a cloud built to run on-premise (within a company’s hardware), or in any of the various public clouds. Then you need to be able to connect and orchestrate the containers (and deliver on that actual scalability), and Kubernetes<\/a> is the standard for that. If you’re not building containers, and containers for Kubernetes, you’re risking a lot of lock-in: getting stuck using technology that doesn’t scale, isn’t flexible, or isn’t portable in the ways you’re going to want.<\/p>\n

The Question<\/h2>\n

The question then becomes, which bank do you use?<\/em> Where do you store your gold – the implementation of your competitive advantage – where you can have usability, but also portability and the right to find a different platform if you want to? And, for bonus points, since developers and the teams that surround them are the linchpin<\/a> in all of this, how do you do all of that in a way that makes those developers and those teams super happy?<\/p>\n

OpenShift!<\/h2>\n

We could<\/em> be accused of being biased at this point, we do<\/em> both work for Red Hat. But even before we worked for Red Hat, we loved OpenShift – and loving it as much as we do is how we ended up at<\/em> Red Hat. The more we work with a variety of customers, the more we see that the beauty of a platform like OpenShift, and the ecosystem and partnerships that surround it, is that you can build a container stupid easy<\/em> (using Red Hat’s source-to-image (s2i) technology), using implementations and frameworks you know and love (JEE, Spring Boot, NodeJS, etc…) or even architectures that give you even more power and scalability (Quarkus, Camel-K), and you can deploy that container anywhere you’d want to run it<\/em>: AWS, GCS, IBM or Microsoft’s cloud, or on-premise in your own private cloud.<\/p>\n

You end up locked into OpenShift – but only<\/em> OpenShift. You have to choose\u00a0some<\/em> bank. And OpenShift is built to allow you to move your…well, your gold, wherever you want it to be.<\/p>\n

TL;DR<\/h2>\n

A company’s applications are very much like gold – they’re wealth realized from raw materials. Protect your gold.<\/strong> Protect your rights to access and use your gold in the ways that will realize the most inherent value – and give you room to find\u00a0more<\/em> value than you even guessed was there. In the world of application development, that translates to open standards, source control, releasing frequently, and containers – Kubernetes and OpenShift, specifically. All of this works to help make sure that your applications, the execution of your competitive advantage, are as protected and valuable as they can be.<\/p>\n","protected":false},"excerpt":{"rendered":"

We’ve talked previously about how developers drive organizational success: they deliver the applications by which companies deliver their competitive advantages. Because they are a way for companies to deliver products to customers, those delivered applications are critically valuable. Application development is a lot like extracting gold – it creates value out of raw resources. Application … <\/p>\n

Read More Read More<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[28,4],"tags":[132,154,45,88,82,129,87,155,57,44,153],"wf_post_folders":[],"coauthors":[26,11],"class_list":["post-2785","post","type-post","status-publish","format-standard","hentry","category-organizations","category-technology","tag-architecture","tag-containers","tag-continuous-delivery","tag-cri-o","tag-docker","tag-git","tag-kubernetes","tag-lock-in","tag-only-one-safe","tag-openshift","tag-scaling"],"_links":{"self":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2785","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/comments?post=2785"}],"version-history":[{"count":7,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2785\/revisions"}],"predecessor-version":[{"id":3028,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/2785\/revisions\/3028"}],"wp:attachment":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/media?parent=2785"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/categories?post=2785"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/tags?post=2785"},{"taxonomy":"wf_post_folders","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/wf_post_folders?post=2785"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/coauthors?post=2785"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}