* Append "Policy" to the end of the names of your sagas. * Use commands for things you want to happen. * Use the imperative for naming your commands, e.g., SendWelcomeEmail. * Use classes for commands. * Use events for things that have happened. * Use interfaces for events. * Event names are often the past
Here are some common queries I use in Postgres. View Current Query Activity SELECT query, state, * FROM pg_stat_activity Drop Existing Connections Except Yours (9.2+) SELECT pg_terminate_backend(pg_stat_activity.pid) FROM pg_stat_activity WHERE pg_stat_activity.datname = 'TARGET_DB' -- ← change this to
Naming resource groups and resources in Azure in a consistent manner is challenging. The naming guidance by Microsoft [https://docs.microsoft.com/en-us/azure/architecture/best-practices/naming-conventions] is quite good and is a good starting point. Naming Resource Groups In most modern systems you will have resource groups for each
When building my Android project I am getting this error message. > Checking the license for package Android SDK Build-Tools 25.0.3 in C:\Android\android-sdk\licenses Warning: License for package Android SDK Build-Tools 25.0.3 not accepted. Checking the license for package Android SDK Platform 25 in C:
In order to build a successful micro service architecture we must keenly aware of the issues that can cause distributed systems to fail. In the 90's a smart set of researchers at Sun Microsystems summarized the most common pitfalls people run into when building distributed systems. These pitfalls are today
Database Migration RoundhousE [https://github.com/chucknorris/roundhouse] DbUp [https://dbup.readthedocs.io] Inversion of Control Container Autofac [https://autofac.org/] Logging Serilog [https://serilog.net/] NLog [http://nlog-project.org/] Mapping AutoMapper [https://automapper.org/] Mediator/Command Handler/Pipeline MediatR [https://github.com/jbogard/MediatR] Testing XUnit [https://xunit.github.
The de facto loggers in the .NET space have historically been log4net and NLog. Along comes Serilog and it has a more metadata"y" approach that they describe as structured events. Serilog fits in extremely well with modern aggregated logging services like Elastisearch, Loggly, etc... Logging Goals: * Upon application start,
When building a Continuous Integration/Continuous Deployment pipeline in Azure it's important to plan out your resource groups ahead of time. The unit of containment in Azure for a resource, e.g. database, VM(virtual machine), or blob storage, is a RG(resource group). Resource Group Facts 1. When you
Thanks to Swagger and the ecosystem surrounding Swagger it's straight forward to develop great documentation for your ASP .NET Core Web APIs. There is a .NET/C# project called Swashbuckle that will generate Swagger compatible documentation and output html documentation. The Swashbuckle project for ASP .NET Core is called Ahoy
Slack [https://slack.com/] is the new hotness in team IM (instant messaging) tools. It is a great business communication tool that can greatly improve communication within your organization. Slack features the ability to add and remove people from an organization much like Github. You really only need one account.
I took several courses on Abstract Algebra as an undergrad and graduate student in college. One core aspect of Abstract Algebra that we studied was Group Theory. Group theory is an underpinning of Category theory which has shown up quite a bit in programming lately with linq and functional programming.
This blog post just didn't want to get out the door so it's being published almost half a year late:) I published a Windows 8 app, Pixel Hero [http://apps.microsoft.com/windows/en-us/app/pixel-hero/8742b5e0-0d30-4cb1-90fc-0a9010fb6023] late Saturday night (9/7/2013) into what is now called the Windows