Wow, thanks @vnorby! That was my team. We started out in the beginning of 2007 with myself and 2 other devs and we were just the "API Team". Our goal was to simplify and standardize data access for all front-end features. At that time, this was a monumental task as most features lacked common code besides the infamous MaintenanceConfig. There was basic SQL call wrappers for querying data and some core handling of the large number of federated profile/mail DBs, but besides that, features tended to be built ad hoc.
This posed a problem to scaling the massive web traffic load on these databases. It also left open dangerous patterns of duplicate data calls where each control on a page was making its own calls for the data it would bind to.
Man... I could go on for days about the path we took from the wild wild west of code slinging up to the nice accessible, maintainable, freakin' BEAUTIFUL Server Slayer platform. Instead, let me just leave you with the logo we designed for this internal platform: http://imgur.com/Pvpy7
\m/
-- robbie
API Development Mgr.
MySpace 2/2007 - 3/2010
This posed a problem to scaling the massive web traffic load on these databases. It also left open dangerous patterns of duplicate data calls where each control on a page was making its own calls for the data it would bind to.
Man... I could go on for days about the path we took from the wild wild west of code slinging up to the nice accessible, maintainable, freakin' BEAUTIFUL Server Slayer platform. Instead, let me just leave you with the logo we designed for this internal platform: http://imgur.com/Pvpy7
\m/ -- robbie API Development Mgr. MySpace 2/2007 - 3/2010