<commit_before>---
published: true
title: A Definition of Enterprise Computing
layout: post
---
# A Working Definition of Enterprise Computing\n\nSince I\'m likely to be talking about it in other postings, I\'ll define what\nI mean by Enterprise Computing.\n\nIn my way of thinking, I don\'t consider customer-facing applications --\nregardless of size or arrival/throughput rates -- as Enterprise Computing\napplications.  Critical, complex, a vital component of some business\nmodels, yes.  But customer-facing fashion is fickle and rapidly changing,\nand that should be built into the application expectations regarding\nlongevity and costs for rewrites.  Now the underlying architecture and\ntools that support those ... Now we\'re talking.\n\nA further pre-note:  Developer-oriented, publicly exposed API\'s fall into\nthe same category.  These are products, not: *The infrastructure that an\nongoing business relies upon in order to promote and deliver its products.*\n\n## Enterprise Computing:\n*Maintains central repositories of organization-wide data\n*Provides access to data and services used by internal and external facing\napplications\n*Is required to provide for the needs of multiple sub-organizations with\nguidance and support for common infrastructure, architectures, standards,\nprocedures and technical capabilities\n*Is subject to an eternal pendulum balancing between centrailzed vs.\ndecentralized decision making and authority\n*Provides the infrastructure and standards to support all of the above, and\nincluding required cross-application messaging support\n*Is expected to provide a high level of stability, consistency,\nreliability, and longevity<commit_msg>Post update: A Definition of Enterprise Computing<commit_after>---
published: true
title: A Definition of Enterprise Computing
layout: post
---
# A Working Definition of Enterprise Computing

Since I'm likely to be talking about it in other postings, I'll define what I mean by Enterprise Computing.

In my way of thinking, I don't consider customer-facing applications -- regardless of size or arrival/throughput rates -- as Enterprise Computing applications.  Critical, complex, a vital component of some business models, yes.  But customer-facing fashion is fickle and rapidly changing, and that should be built into the application expectations regarding longevity and costs for rewrites.  Now the underlying architecture and tools that support those ... Now we're talking.  

A further pre-note:  Developer-oriented, publicly exposed API's fall into the same category.  These are products, not: **The infrastructure that an ongoing business relies upon in order to promote and deliver its products.**

## Enterprise Computing:
* Maintains central repositories of organization-wide data
* Provides access to data and services used by internal and external facing applications
* Is required to provide for the needs of multiple sub-organizations with guidance and support for common infrastructure, architectures, standards, procedures and technical capabilities
* Is subject to an eternal pendulum balancing between centrailzed vs. decentralized decision making and authority
* Provides the infrastructure and standards to support all of the above, and including required cross-application messaging support
* Is expected to provide a high level of stability, consistency, reliability, and longevity
{'fraction_non_alphanumeric': 0.05156157925751326, 'fraction_numerical': 0.0, 'mean_word_length': 5.172727272727273, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3871298', 'n_tokens_mistral': 778, 'n_tokens_neox': 721, 'n_words': 426}