February 13, 2016 at 12:12 pm
Comments posted to this topic are about the item Zero Downtime for 2016
February 15, 2016 at 4:23 am
You are only as strong as your weakest component.
If you want zero downtime then your components have to support that. To an extent you can engineer around some limitations.
There is also the use to which the components are put. A change in the business usage of the technology stack may change its ability to give you zero downtime.
February 15, 2016 at 5:32 am
Unless it is a business requirement Zero Downtime is too expensive a goal to achieve. If it is a business requirement then a Cost/Benefit analysis can be done or at least some kind of business justification.
The complexity of a Zero Downtime solution is unlikely to be cost neutral and also unlikely to be without its own risks. As such it should not really be an internally driven requirement.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 8, 2016 at 4:56 pm
Yes, we need to deal with our index overload.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply