This Blog skyliner does a good job talking about a need for software development to move from monolithic code to smaller changes which are pushed to production more frequently.
It still seems no matter what methodology of software cycle development lifecycle followed it includes some level of definition, development, QA, UAT, and Production Release. Somewhere in the process there is a merge of multiple items into a release. This still means your release to production could be monotholic. Even Google and Facebook which revolutionized the concept of Continous Integration (CI) and release fixes daily, only release major updates once a week.
Reading the blog left me with the question is the future of CI, to release single items to production, validate over a defined period of time and push the next release? This entire process would happen automatically based on a queue(FIFO) system.
That would imply that the if you run code across a SaaS platform that platform would support a Facebook like update where code would be pushed and updated while the existing code continues to handle the requests and the users wouldn’t see discrepancies, some validation would happen, code would activate and a timer would start on the next release.
Is this really a reality?