Difference between revisions of "PracOps"
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[PracOps]] is a technical philosophy developed by [[Robert Brockway]] |
+ | [[PracOps]] is a technical philosophy developed by [[Robert Brockway]]. |
== Backups == |
== Backups == |
||
| Line 10: | Line 10: | ||
== Comprehension == |
== Comprehension == |
||
| + | |||
| + | Humans should be able to fully understand the functioning of a system. |
||
== Consistency == |
== Consistency == |
||
Environments should be as consistent as feasible. Avoid exceptions where feasible. |
Environments should be as consistent as feasible. Avoid exceptions where feasible. |
||
| + | |||
| + | == Hosting == |
||
| + | |||
| + | Both self-hosted and outsourced solutions should be considered. Many organisations today have a policy to only outsource. As a result solutions are outsourced even when cheaper and more reliable self-hosts solutions exist. |
||
| + | |||
| + | For decades IT has swung between insourcing and outsourcing. Since approximately 2014 IT has been experiencing extreme outsourcing even when it is counterproductive. |
||
== Licencing == |
== Licencing == |
||
| − | Use [[FOSS]] whenever it is practical to do so. Non-FOSS can be used when no reasonable FOSS solution exists. |
+ | Use [[FOSS]] whenever it is practical to do so. Non-FOSS can be used when no reasonable FOSS solution exists. This is true for both insourcing and outsourcing. |
== Monitoring == |
== Monitoring == |
||
| Line 25: | Line 33: | ||
== Purpose == |
== Purpose == |
||
| − | An organisation should implement a solution which meets their needs. Too many organisations just do what other, often larger, organisations do. As a result many computer systems are much more expensive, complex and unreliable than they need to be. |
+ | An organisation should implement a solution which meets their needs and is fit for purpose. Too many organisations just do what other, often larger, organisations do. As a result many computer systems are much more expensive, complex and unreliable than they need to be. |
Many organisations can estimate maximum loads. Eg, in general a government department providing a service in a jurisdiction knows that the maximum number of people who can use their service is the number of people who reside in the jurisdiction. Provisioning a service which can scale far past this, or even only becomes economical at scales beyond the size of the jurisdiction is suboptimal. |
Many organisations can estimate maximum loads. Eg, in general a government department providing a service in a jurisdiction knows that the maximum number of people who can use their service is the number of people who reside in the jurisdiction. Provisioning a service which can scale far past this, or even only becomes economical at scales beyond the size of the jurisdiction is suboptimal. |
||
| Line 40: | Line 48: | ||
== Simplicity == |
== Simplicity == |
||
| + | |||
| + | As simple as possible while still achieving their operational objectives reliably. |
||
{{Draft}} |
{{Draft}} |
||
Latest revision as of 04:27, 13 April 2024
PracOps is a technical philosophy developed by Robert Brockway.
Backups
Change
Change of the sake of change is bad.
There is such a thing as feature completeness.
Comprehension
Humans should be able to fully understand the functioning of a system.
Consistency
Environments should be as consistent as feasible. Avoid exceptions where feasible.
Hosting
Both self-hosted and outsourced solutions should be considered. Many organisations today have a policy to only outsource. As a result solutions are outsourced even when cheaper and more reliable self-hosts solutions exist.
For decades IT has swung between insourcing and outsourcing. Since approximately 2014 IT has been experiencing extreme outsourcing even when it is counterproductive.
Licencing
Use FOSS whenever it is practical to do so. Non-FOSS can be used when no reasonable FOSS solution exists. This is true for both insourcing and outsourcing.
Monitoring
The purpose of monitoring is to describe the bonunds of the running system, not merely to detect specific failure more. Properly configured a monitor will alert when the behaviour of the system moves outside the pre-defined limits. These limits could be statically or dynamically assigned.
Purpose
An organisation should implement a solution which meets their needs and is fit for purpose. Too many organisations just do what other, often larger, organisations do. As a result many computer systems are much more expensive, complex and unreliable than they need to be.
Many organisations can estimate maximum loads. Eg, in general a government department providing a service in a jurisdiction knows that the maximum number of people who can use their service is the number of people who reside in the jurisdiction. Provisioning a service which can scale far past this, or even only becomes economical at scales beyond the size of the jurisdiction is suboptimal.
Reliability
Unscheduled outages should be minimised. A concerning trend in IT since 2010 is to acclimate users to outages and failures. Users should expect more of the computer systems they use.
Pracops argues that computers are ultimately tools. Tools that require excessive maintenance to work are not good tools.
People expect their car to start on demand but apparently accept far more failures from general computer systems.
Data from the Uptime Institute clearly shows that outages are getting longer.
Simplicity
As simple as possible while still achieving their operational objectives reliably.
This is a draft article and so will not be published on A Voice for Men or appear in random article selections. Wiki4Men is looking for trustworthy editors that can turn draft articles in to featured articles. Information on how to apply is on the Main Page.