Loading ...
Sorry, an error occurred while loading the content.

Re: [XP] The consequences of shortening release cycles

Expand Messages
  • George Dinwiddie
    ... Yeah, that could be a problem. Unless you run a distributed database with an instance on each server box. It could be done... - George -- ... * George
    Message 1 of 35 , Nov 13, 2009
    • 0 Attachment
      Tim Ottinger wrote:
      >
      > ----- Original Message ----
      >> From: George Dinwiddie <lists@...>
      >> Just thinking... You could have two environments with a load balancer in
      >> front. Keep one environment offline with the load balancer, deploy to
      >> that, and switch which one is live. If the load balancer was set to
      >> keep a given session on the same machine, then current sessions would
      >> continue on the old system after deploying the new.
      >>
      >
      > My only worry is when the deployment includes a schema migration. I'm
      > not sure how to do continuous deployment in the old RDBMS case. Maybe
      > that is the real promise of CouchDB and its ilk. I'm betting CD is
      > easier if you have adapted (or, I suppose, planned) the architecture
      > to support it.

      Yeah, that could be a problem. Unless you run a distributed database
      with an instance on each server box. It could be done...

      - George

      --
      ----------------------------------------------------------------------
      * George Dinwiddie * http://blog.gdinwiddie.com
      Software Development http://www.idiacomputing.com
      Consultant and Coach http://www.agilemaryland.org
      ----------------------------------------------------------------------
    • George Dinwiddie
      ... Yeah, that could be a problem. Unless you run a distributed database with an instance on each server box. It could be done... - George -- ... * George
      Message 35 of 35 , Nov 13, 2009
      • 0 Attachment
        Tim Ottinger wrote:
        >
        > ----- Original Message ----
        >> From: George Dinwiddie <lists@...>
        >> Just thinking... You could have two environments with a load balancer in
        >> front. Keep one environment offline with the load balancer, deploy to
        >> that, and switch which one is live. If the load balancer was set to
        >> keep a given session on the same machine, then current sessions would
        >> continue on the old system after deploying the new.
        >>
        >
        > My only worry is when the deployment includes a schema migration. I'm
        > not sure how to do continuous deployment in the old RDBMS case. Maybe
        > that is the real promise of CouchDB and its ilk. I'm betting CD is
        > easier if you have adapted (or, I suppose, planned) the architecture
        > to support it.

        Yeah, that could be a problem. Unless you run a distributed database
        with an instance on each server box. It could be done...

        - George

        --
        ----------------------------------------------------------------------
        * George Dinwiddie * http://blog.gdinwiddie.com
        Software Development http://www.idiacomputing.com
        Consultant and Coach http://www.agilemaryland.org
        ----------------------------------------------------------------------
      Your message has been successfully submitted and would be delivered to recipients shortly.