Writing enterprise ready software

X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/9a4b98c00c3afae5e5948aed5995ebd1d51d4319..8e2f217b2f7824a624e6f173fdf79231dba7baf4:/mypapers/enterprise-software/enterprise-software.html diff --git a/mypapers/enterprise-software/enterprise-software.html b/mypapers/enterprise-software/enterprise-software.html index 86d7eb4f19..6aa8d46ff7 100644 --- a/mypapers/enterprise-software/enterprise-software.html +++ b/mypapers/enterprise-software/enterprise-software.html @@ -1,10 +1,12 @@ + + Writing enterprise ready software @@ -29,7 +31,7 @@

We are in trouble

Some thinks are possible for 1 to 10 machines, and impossible with +

Some things are possible for 1 to 10 machines, and impossible with 500 machines. What do you do when you break the ssh configuration file on 700 machines? @@ -76,7 +78,7 @@ long time ago, and the program is still used in production. --> full, one do not want to kick out 30000 users to take down the database and resize the file system.

Disktrouble

Disk trouble

RAID is only only useful until the last redundancy disk is lost. @@ -95,7 +97,7 @@ painful and prone to errors.

Trying to get some network server to work when it require to use some given port range, which is already taken by some other service -and blocked in the router -- or try to get the coorporate network +and blocked in the router -- or try to get the corporate network gatekeeper to open up the firewall

Version trouble

@@ -105,7 +107,7 @@ PHP usable with all of these?

Usability trouble

When starting a program from the meny, where does it go if nothing +

When starting a program from the menu, where does it go if nothing appear on the screen?

Do users always read their ~/.xsession-error file? @@ -126,11 +128,17 @@ appear on the screen? the operations needing root access. (build / configuration as well)

make sure the software can be installed anywhere (location - independent), avoid hardcoding paths into the binaries. + independent), avoid hard coding paths into the binaries.

make the source available to make it possible to fix problems on site, and to use it on different platforms (os/hw) in the future + + +

More tips

+ +

Make paths into users home directories relative to ~user/, as users will move from disk to disk, or copy their home directory from site to site. Always convert paths when saving config files. @@ -139,7 +147,7 @@ appear on the screen? extra library in place
use well known libraries instead of making your own implementation. - reduses the security risk. + reduces the security risk.
make sure libraries, and programming languages are backwards compatible. @@ -147,6 +155,12 @@ appear on the screen?
use a well known license. it is a pain to evaluate every new license +

+ +

Make it easier for everyone

+ +

when distributing source, do not use vendor specific compiler features. It will not work with the other vendors compilers used to compile on site. @@ -163,14 +177,22 @@ appear on the screen?
system services should send messages to syslog. always log why when crashing. always log problems and errors. -
reuse configuration. ktouch have its own x layout setting. +

+ +

Final clues

+ +

reuse configuration when possible. ktouch have its own x layout setting. better to fetch the current one from X like xkeycaps. -
providing hooks to the local admins +
providing hooks to the local administrators
reduce flexibility. trying to support people over the phone when the gui is different for every person is a pain. +
do not try to cleverly find the final resting place of the installation. +

Solving the upgrade problem using multilevel @@ -180,7 +202,9 @@ appear on the screen?
local configuration should be kept during upgrades
-
easiest to do if the local configration is separate from the +
do not change configuration file format
+ +
easiest to do if the local configuration is separate from the package default
several actors what to have a say in the service @@ -199,8 +223,6 @@ appear on the screen? - -
Thank you very much

Questions?