Disney Channel used to be a premium, ad-free channel.
3,447 karma · joined June 10, 2012
http://josephdaigle.me
https://github.com/jdaigle
https://twitter.com/JosephDaigle
http://stackoverflow.com/users/507/joseph-daigle
Disney Channel used to be a premium, ad-free channel.
It might not work for everyone or every team, but it sometimes works for me.
Practically speaking, I find that abstracting a system into a set of commands and a set of queries (i.e. CQRS) is often the "right" solution. Each command/query encapsulates an individual use-case, and all of the business rules and database access required.
Already exists: https://msdn.microsoft.com/en-us/magazine/mt614271.aspx
But I do a lot more these days with https://www.linqpad.net/ instead.
Interestingly, however, most of their "open source" efforts (.NET, C#, and related) are all on GitHub rather than their own hosted offerings: CodePlex (which is basically dead) or "Visual Studio Team Services".
I seem to recall that Microsoft has previously used a custom Perforce "fork" for their larger code bases (Windows, Server, Office, etc.).
Granted, I learned git first and had been using it for 6 years before using hg.
We too use hg for our code. But I wouldn't say we "love" it - it works and we haven't found a compelling reason to switch.
So I'm curious, what about hg makes it great for some projects?
Therefore it's important to capture and analyze performance metrics _from production_. A really good commercial tool is SQL Sentry (http://www.sqlsentry.com/). You can, of course, patch together your own tooling from open source and homegrown solutions.
Can you elaborate on this; both how it helps and why you're using C# for database migrations?
I guess the tradeoff is that with ELB/ALB, like most PaaS, you don't have to "manage" your load balancer hosts. And it's probably cheaper than running an HAProxy cluster on EC2.
But for the power you get with HAProxy, is it worth it?
Does anyone have experience running HAProxy on EC2 at large scale?
I don't think that's a fair assessment given the what is now minimum expectations around syntax highlighting, syntax/grammar validation, autocomplete, etc. We're no longer dealing with "plain text".