This is just a quick Moleskine-style scribble page to start thinking about various "enterprise" features.

Daisy for ASPs

ASP = Application Service Provider.

I'm an ISP and I want to offer self-managed Wikis or websites to my customers, using Daisy.

  • I want to run several Daisies on a single machine:
    • each user gets its own repo/wiki combo, and could perhaps share the messaging machinerie
    • add multi-tenancy concepts to the repo server
    • start several wikis or repo servers in a single VM
    • users should only care about their local config, content and user management data, while a machine administrator might want a conglomerate (over)view
    • running several Daisies alongside each other presents a considerable footprint in terms of deployed VMs (memory) and port allocation
  • Users shouldn't be aware of the fact that they share a machine or a single Daisy installation.
  • Users should be able to manage every aspect of their Daisy installation without shell access
    • sites configuration
    • skin editing
    • (re)start/stop repo/wiki
  • Updates to the installed Daisy versions should be easy:
    • for people who sign up for a hosted version of the "latest and greatest" version of Daisy
    • for people who want to stick with the version of Daisy they know and love, and only want to upgrade according their own pace
  • Contingency and deployment management issues
    • (dated) backups and restore
    • export and import tools (for refugee users)

High availability and scalability

I'm using Daisy and need high availability. Or I will host a high-profile website/Wiki.

  • Hot stand-by copy of a Daisy installation: how-to?
  • Load-balancing
    • Wiki / website: it is possible out of the box to have several Wikis connect to a single repo server
      • how would they share the same sites configuration, given that this currently must be configured inside their individual webapps?
    • Repo server? Can this be mirrored or hot-stand-by'ed at all?
    • Database and parts / index store synchronization?
    • How to reuse the messaging subsystem to turn change events into synchronization events?

Fields

NameValue
CategoryDesign documents & proposals