Solving Big Business Problems In Our Little Toolbox Application. A Use Case For Project Distributor.

Project Distributor: Introduction to our distributed web service model
So Darren and I have put in about a month now on the Project Distributor website. We are starting to reach that critical point where the site is pretty cool, we have plenty of users, we are thinking about running out of the allowable bandwidth for the demo site, and all sorts of other things that tend to happen all at once. Now, there are some problems you can design yourself out of, and others that you really have to throw some money at. Our latest enhancements can be summed up in a short list.

• Buy a domain name and start hosting in two places. Project Distributor.com should be up fairly soon to accompany people host their own versions of the application. And that means a big source release is in the future. At this juncture risk fragmentation.
• Design away fragmentation with a series of ingenious features that will make everyone want to use the application at hand.

I’m here to talk about the last two, since Darren already bought some additional hosting for us. The concept will be to release a fairly stable version of the application so that groups can host tools, code snippets and other source/binary releases for their teams to share. The application is very lightweight and easy to set-up, so it won’t require a bunch of hand holding and configuration to get up and running initially. From our standpoint we solve a number of issues at this juncture. The most obvious problem is what we classify the Lutz Roeder use case..NET Reflector is the key type of application we’d love to get hosted because it makes it a bit easier to find, not that Google does a bad job, we’d just like to get a bunch of tools in one place, with some features for feedback, new releases, and some cool client tools for publishing.

Authored by simma1990. Hosted by Edublogs.