× Products Applications Services Partners Support Contact Log-in

Continuous vs. Batch Updates

Keywords: Whitelabel, Continuous, Batch, Updates, Release Notes


Summary:

Choosing between Continuous updates and Batch updates



Monnit® offers you the choice of 2 processes for managing portal updates and timing of adding new features. These processes will keep your portal up to date, while making it more functional.

The first process, called Continuous Update will sync your portal to the same features available in www.iMonnit.com. The portal will be updated continually with the newest features at the same time as the iMonnit® site. As soon as we complete a new feature or update, it will be automatically added to your portal. You will be informed of the update and will be provided a description of the changes by a release note page which will be available on your first log in after the release. This option is preferred for partners who want to remain on the leading edge of new sensor technologies as well as portal enhancements.

The second process or Batch Update will be geared toward those who want to release formal documentation about new features before they are released.  The same features will be included in these updates but the updates will be much less frequent.  You will be notified in advance of any updates which will be made or features that will be updated or added, along with a release date.  There will be a period of time between the notification and the release date to allow for documentation to be updated.

Selecting which path your portal utilizes is controled by you and can be switched back and for as need dictates.  Controlling with codebase your portal uses is as easy as configuring the A-Record that you set up to point your domain to our loadbalancers.  
To point your domain to the Continuous Update servers configure the A-Record to point to: 192.41.40.115 
To point your domain to the Batch Update servers configure the A-Record to point to: 192.41.40.114


Below is an example of how the two processes work together.  For simplicity sake we will assume one new feature or enhancement is completed each month. (Timeframes used are for illustrative purposes only, actual time frames will vary based on features being released)


In January the first update is complete it is deployed to all portals using Continuous Updates.

In February the second update is complete it is deployed to all portals using Continuous Updates.

In March the third update is complete it is deployed to all portals using Continuous Updates.  The portals using Batch Updates will receive a notification of the three updates along with a go live date of May.

In April the fourth update is complete it is deployed to all portals using Continuous Updates.

In May the fifth update is complete it is deployed to all portals using Continuous Updates.  The portals using Batch Updates will receive the first three updates at this time.

In June the sixth update is complete and is deployed to all portals using Continuous Updates. The portals using Batch Updates will receive a notification of updates 4-6 along with a go live date of August.

In July the seventh update is complete and is deployed to all portals using Continuous Updates.

In August the eight update is complete and is deployed to all portals using Continuous Updates.  The portals using Batch Updates will receive updates 4-6

And continues…


If you have additinoal questions feel free to contact support@monnit.com and we are happy to answer questions.



Related Articles