Describing Continuous Delivery (Without Using the Term)
From Tom DeMarco’s article Software Engineering: An Idea Whose Time Has Come and Gone? [PDF]:
You say to your team leads, “I have a finish date in mind, and I’m not even going to share it with you. When I come in one day and tell you the project will end in one week, you have to be ready to package up and deliver what you’ve got as the final product. Your job is to go about the project incrementally, adding pieces to the whole in the order of their relative value, and doing integration and documentation and acceptance testing incrementally as you go.”
DeMarco isn’t recommending specific methodologies like Agile, but
this is a pretty good business oriented description of Continuous
Delivery without continuous (production) deployment.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)






Comments
Fahmeed Nawaz replied on Tue, 2012/06/12 - 11:11am
FSYNC_SAFE creates a WriteConcern using WriteConcern( 1, 0, true) which is what you are looking for.
Note that if you use fsync on all writes, and you app is write intensive, it will affect the performance quite a bit.
If so you may want to also look into using journaling on the server.