Skip to content

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


Follow @CodeOpinion

Continuous Integration vs Continuous Delivery vs Continuous Deployment

Continuous Integration is a term/buzzword that seems to have a clear understanding.  Continuous Delivery and Continuous Deployment on the other hand, seem to get incorrectly interchanged. Continuous Integration Continuously integrate changes into source control in order to test changes through automated builds and unit tests.  This provides developers with early warnings of broken code/merges and allows them to fix problems continuously. Continuous Delivery Some have the opinion that continuous delivery is when you deliver to a user base, such as UAT or QA.  I personally disagree.  Continuous delivery is about making sure your software is always production ready. via Jez… Read More »Continuous Integration vs Continuous Delivery vs Continuous Deployment

SQL Server Transaction Log File (LDF) Misconception

A common misconception is that setting the recovery model to simple will cause SQL Server not to use the transaction log file (LDF), preventing it from growing to an abnormal size. In fact, the simple recovery model will still use the transaction log when performing transactions, however it will reclaims log space to keep space requirements small. The actual file size will not be reduced by reclaiming space.  Same as performing a transactional backup will not reduce the actual file size. This is important becase if you have a long running transaction that is performing many insert/update/delete statements, the transaction… Read More »SQL Server Transaction Log File (LDF) Misconception