Monday, July 1, 2013
My recent publications on InfoQ.com
Introducing DevOps to Traditional Enterprises - Niek Bartholomeus recently finishing composing a four post DevOps focused blog series about leading the implementation of configuration management and release management in a traditional enterprise. Niek covers the theory of DevOps, then an analysis of the problems with software delivery within a traditional enterprise, and finally the application of specific DevOps practices. Jun 23, 2013
Friday, April 19, 2013
Remove a git sub-module (How to)
How to remove a submodule (Excerpt from https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial#Removal)
1. Delete the relevant line from the .gitmodules file.
2. Delete the relevant section from .git/config.
3. Run git rm --cached path_to_submodule (no trailing slash).
4. Commit the superproject.
5. Delete the now untracked submodule files.
1. Delete the relevant line from the .gitmodules file.
2. Delete the relevant section from .git/config.
3. Run git rm --cached path_to_submodule (no trailing slash).
4. Commit the superproject.
5. Delete the now untracked submodule files.
Saturday, March 9, 2013
TCP vs UDP, First Opsschool Curriculum Pull Request
This is my first contribution to the Opsschool Curriculum, my pull request is currently queued for review. Please comment on it through GitHub's utilities if you think the sub-section can be improved. The following is the sub-section submitted if you would just like to read about TCP vs UDP.
TCP vs UDP
Both TCP :rfc:`793` and UDP :rfc:`768` provide data transfer between processes through ports. Those process ports can be on the same computer or separate computers connected by a network. TCP provides the following: reliability, flow control, and connections. (UDP does not) This means TCP will be sending more header data, more packets between ports and doing more processing to provide its capabilities. UDP requires less header data in the individual packets and requires less packets on the network to do its work. However, because UDP does not guarantee reliability, UDP allows for packets not getting communicated end to end after leaving the sender. The choice of protocols to use is often based on whether the risk of losing packets in real-time without immediate alerting is acceptable. In some cases UDP may be acceptable, such as video or audio streaming where programs can interpolate over missing packets. However, TCP will be required because of its guarantees in systems that support banking or healthcare.
An example of the difference between the two protocols that will help us understand the tradeoffs is a comparison of what it takes to send the first data byte. TCP requires an initial "three way handshake" in order to begin sending data. That amounts to one initial packet sent between ports from initiator of the communication to the receiver, then another packet sent back, and then a final packet sent from the initiator to the receiver again. All that happens before sending the first byte of data. In UDP the first packet sent contains the first byte of data.
Another example of the difference between the protocols is the size of the headers of the two protocols. The TCP header is 20 bytes and the UDP header 8 bytes.
TCP vs UDP
Both TCP :rfc:`793` and UDP :rfc:`768` provide data transfer between processes through ports. Those process ports can be on the same computer or separate computers connected by a network. TCP provides the following: reliability, flow control, and connections. (UDP does not) This means TCP will be sending more header data, more packets between ports and doing more processing to provide its capabilities. UDP requires less header data in the individual packets and requires less packets on the network to do its work. However, because UDP does not guarantee reliability, UDP allows for packets not getting communicated end to end after leaving the sender. The choice of protocols to use is often based on whether the risk of losing packets in real-time without immediate alerting is acceptable. In some cases UDP may be acceptable, such as video or audio streaming where programs can interpolate over missing packets. However, TCP will be required because of its guarantees in systems that support banking or healthcare.
An example of the difference between the two protocols that will help us understand the tradeoffs is a comparison of what it takes to send the first data byte. TCP requires an initial "three way handshake" in order to begin sending data. That amounts to one initial packet sent between ports from initiator of the communication to the receiver, then another packet sent back, and then a final packet sent from the initiator to the receiver again. All that happens before sending the first byte of data. In UDP the first packet sent contains the first byte of data.
Another example of the difference between the protocols is the size of the headers of the two protocols. The TCP header is 20 bytes and the UDP header 8 bytes.
Subscribe to:
Posts (Atom)