This is for anybody out there looking for information on TeamSnippets since you are considering using it. Short version; I don't see why you would want to use such a service.
When I first started to learn Go a few months ago I compared a lot of things to things that was familiar to me; C#. And I decided to make a series of posts explaining some go-isms in C# (or .Net) terms as well as high-light some of the differences that are important to know about.
Well sometimes I'm lucky and somebody else writes something so I don't have to. Since you should assume that your system will be breached eventually you should make sure that your user's passwords cannot be exposed as a lot of users reuse their passwords across multiple sites.
So I start this series of updated old opinions and the MSDN blog change interface so there are no longer links to monthly archives except the last three months of posts. There is some logic to it I guess since it keeps the archive list shorter but I wish they made it configurable... Anyway; this time it is time to talk about some posts from July 2008 which can be found on this page.
Over the last few weeks I've been going over a few different ways to solve inter service communication. So which one is best then?
In order to distinguish pub/sub from message bus communication I will assume the pub/sub does not use another component to distribute the data as that would be a message bus pattern. I will assume that the publisher knows about all subscribers either statically or dynamically.
So time to look back again and update some old opinions from June 2008. And while there are some other useful stuff in there I'll focus on code coverage and testing simple things. Because I feel the urge to explain myself...
Feature toggles can be used for several reasons. They can be used to avoid branching (for some people that is important), test things in production, A/B testing, a safety net or to enhance the experience for certain customers. Regardless of what the reason is the basics are the same.