Update:Archive/1.0/Overall Plan

Update: Home Page » Overall Plan

Introduction

The following page will give an overview of what the overall plans are for development and deployment of the UMO service.

Getting our Bearings

We have an application that we do not know what it does fully. In addition, we do not have a clear idea of key policy issues as well as any documentation on the overall architecture of the UMO service. The first two weeks will be spent assessing the situation so that we know what we have and what it does.

Development

Getting to version 2.0

In our discussions on #umo we have talked about a few things in regards to v2.0. The overall opinion is that we should rewrite completely from scratch so as to take advantage of frameworks/tools to scale the application and grow it over time better. The following is a summary:

What language should we use?

Sticking with PHP seems to make the most sense at this time. We have that skill set (both on the development and systems side) and the alternatives are not particularly attractive. We considered both Perl and Java but decided against both at this time. The existing UMO service is currently scaling quite well with over 3 million unique clients a day across 3 servers.

What tools/frameworks should we use?

This is an [[Update:Bestongoing discussion that will hopefully yield the "best tools for the job".