AnthonySteele

/*
 * Example code for my blog post on function shims for NancyFx request handlers
 * Blog post is here: http://anthonysteele.co.uk/more-patterns-for-web-services-in-nancyfx
 */
 
using System;
using System.Collections.Generic;
using System.Threading.Tasks;

using Nancy;

AnthonySteele

using System.Web.Mvc;

namespace FeatureTest
{
	public class FeatureRazorViewEngine : RazorViewEngine
	{
		private const string ViewsPathTemplate = "~/Features/%1/Views/{0}.cshtml";
		private const string LayoutPathTemplate = "~/Features/Layout/{0}.cshtml";

		public FeatureRazorViewEngine() 

AnthonySteele

This document has moved to https://anthonysteele.github.io/AgileValues

I got a lot out of Nathan Gloyn's talk at DDDEA on "Agile: I do not think it means what you think it means".

The slides of the talk are here.

The talk is about where it all went wrong - the mainstream adoption of agile, the brand-name of it, the descent into a cargo cult and the conflict between the principles and the rules.

One thing on slide #29 struck me as odd at the time: Don't be bound by "the rules".

AnthonySteele

##Setup

Many people have the misconception that async and sync code are mutually exclusive. This is not the case. It's easier than it seems!

If you have a method on an interface for async use, then the implementation can have zero or more awaits, and the case with zero awaits covers synchronous implementations. The code below will make this clear.

We have the following example contract that models a processor of messages:

 public class Request

AnthonySteele

This document has moved to: https://anthonysteele.github.io/OptimizationAndMetrics

About optimisation and benchmarks; bottlenecks and what difference optimisation will make.

ASP Kestrel Benchmarks

I heard that the ASP.NET core beta running on Kestrel Web server was capable of processing "over one million requests per second" though a simple benchmark Update: it's nearly 1.2 million now. The full benchmarks are at the bottom of this page

My thoughts were:

AnthonySteele

This document has moved to: https://anthonysteele.github.io/MicroservicesLinks

Links

• The twelve-Factor app
• You need to be this tall to use micro services
• Microservice Prerequisites
• 10 Modern Software Over-Engineering Mistakes

Microservices have a dual nature: On the one hand, they give independence of code, testing, deploy times, versions, tools, techniques, etc. The ability for a team to work on and deploy an isolated unit of functionality when ready is great. It really is an archetectural style for the agile and Continous Deployment era.

AnthonySteele

This document has moved to: https://anthonysteele.github.io/PullRequestWorkflow

The git Pull Request is a powerful tool. But just because you have it, does not mean that you have to use it all the time.

I am thinking of a team that owns on a codebase and works on it regularly. Pull requests give outsiders a powerful thing that they did not have before: controlled access to apply changes that they need, with review by the owners. However it is not a good process to apply across the board to those same owners as a matter of course.

I always think of it as like a gate in an ancient walled city: A stranger can come in, if they pass inspection at the gate. Without the gate, they would be reduced to standing outside and shouting over the wall "We need this feature! And you need to update some urls!" and hope that it happens soon. So the gate allows them to come in and get business done, while res

AnthonySteele

This document has moved to: https://anthonysteele.github.io/AsyncBasicMistakes

I see a lot of code lately that makes some simple mistakes using the async ... await construct.

TL;DR

• A Task is a promise of a value.

AnthonySteele

using System.Net;

namespace JustEat.StatsD.EndpointLookups
{
    public class EndpointData
    {
        private readonly IPEndPoint _ipEndpoint;

        private readonly string _hostName;
        private readonly int _port;

AnthonySteele

I have finally done a like-for-like benchmaerk on JustEat.Statsd version 2.1 versus version 3.1

In order to get a consistent measurement, it has to be on the same machine under the same conditions.

dotnet run -c Release --framework netcoreapp2.0

BenchmarkDotNet=v0.11.0, OS=Windows 10.0.17134.167 (1803/April2018Update/Redstone4)
Intel Core i7-4712HQ CPU 2.30GHz (Max: 2.20GHz) (Haswell), 1 CPU, 8 logical and 4 physical cores