GDS have a blog, and their list of technologies that they use is interesting. Work I've been doing recently means that I've created a similar list of the technologies used within my Information Services team here at the University. For what its worth this what it looks like:
Core servers
We rely on, and in some cases also support, a range of technologies:
- Most services run on virtual machines provided by an internal VMware cluster
- Most run under Linux - SuSE Enterprise, Ubuntu, or Debian
- High-availability clusters use Corosync & Pacemaker
- Servers are built using our internal BES build system
- We have one legacy service using Solaris
- Some services are based on existing software, including phpBB and Mediawiki
- The Web Search service is provided by Funnelback
We rely on, and in some cases also support, a range of technologies:
- Ucam WebAuth, Shibboleth, SAML for web authentication
- LDAP and the University's Lookup service (and its API) for authorisation
- TLS, PKI and X509 certificates for web security
- OpenStreetMap and its API for geographic information
- AbFab, EAP, PAM, and RADUIS as part of investigations into Moonshot
- Google APIs for Google Apps integration
- Netflow for network traffic analysis
- Our current favorite development environment is Python and Django
- Other systems use C, Perl (with HTML::Mason), Java, JavaScript, PHP, Ruby (with Rails)
- System administration relies heavily on shell (normally Bash)
- Our ‘Managed CMS’ service is based on Plone
- Web Sites run under Apache and Tomcat
- MySQL
- PostgreSQL with Slony for replication
- Services are monitored with Nagios
- Collectd collects statistics and Graphite and Grafana visualise them
- Servers are increasingly built and manage with Ansible
- We are moving towards Git (with an internal Gitolite service) for version control, but also use (at least) SVN, CVS, RCS and SCCS!
Posts
No comments:
Post a Comment