Azure Event Grid is a new managed service that was recently released for public review, so I thought I'd take some time out to give it try. It's essentially a cloud scale event routing service, which comes in pretty handy if you're building reactive applications [http://www.reactivemanifesto.org/]. Publishers
If you make considerable usage of constructor injection and the dependency inversion principle [https://en.wikipedia.org/wiki/Dependency_inversion_principle] in your applications, you may eventually run into a situation where you have a fairly long list of dependencies that need to get provided to your class. More often
In a previous post [https://cecilphillip.com/using-consul-for-service-discovery-with-asp-net-core/], I wrote about how to implement client side service discovery with Consul [https://www.consul.io] and ASP.NET Core. It's a very useful technique if you're doing any with containers or microservices. In addition to registering your services, one thing that
One of the benefits of adopting a microservice architectural style is the ability compose applications by bringing together smaller units of functionality (aka services). Not only does it become easier to swap out implementations of an individual service, but it also becomes easier to scale that service too. For example,
The previous post [https://cecilphillip.com/setting-up-webpack-in-asp-net-core-pt-2/] in this Webpack series got you setup in ASP.NET Core, and added features like minifying and hashing to your Webpack bundles. In this post we'll have a look at loaders and how we can use them to add TypeScript support to Webpack.
In the previous post [https://cecilphillip.com/setting-up-webpack-in-asp-net-core], we went through the basics of setting up a Webpack bundle in a new ASP.NET Core application. In this post we'll continue exploring some of the other interesting things we can enable in Webpack. Minifying Your Bundles Bundling your scripts together