Jimmy Bogard - Jimmy Bogard (Page 6)

The False Dichotomy of Monoliths and Microservices

When learning about microservices, you're nearly always introduced to the concept of a monolith. If you're not doing microservices, you're building a monolith. If you're not building a monolith, you must go with microservices. If you're building a monolith, perhaps

ASP.NET Core

Migrating Contoso University Example to Razor Pages

A coworker noticed that it looked like Razor Pages were the new "recommended" way of building server-side rendered web applications in ASP.NET Core 2.0. I hadn't paid much attention because at first glance they looked like Web Forms. However, that's not

Microservices

My Microservices FAQ

Mainly because I get asked all the time about microservices and I'm tired of having to remember on the spot: What is a microservice? A microservice is a service with a design focus towards the smallest autonomous boundary. What is a service? (From Clemens) A service is software

Docker

Containers - What Are They Good For? Local Dependencies

Containers, huh, good god What is it good for? Local Dependencies! * Edwin Starr (also disputed) In the last post, I walked through our typical development pipeline, from local dev to production: Now for most of our developers, when we start a new project, we can just continue to work on

Docker

Containers - What Are They Good For?

Containers, huh, good god What is it good for? Probably something? * Edwin Starr (disputed) Here at Headspring, we're seeing more and more usage of Docker for local development. Having not really touched Docker or containers, I wanted to understand how Docker could help make our lives easier for

respawn

How Respawn Works

This post is mainly a reminder to myself when inevitably I forget what I was doing when designing Respawn. The general problem space is something I've covered quite a lot, but I haven't really walked through how Respawn works internally. The general problem is trying to

respawn

Respawn 3.0 Released

Respawn, the intelligent database deleter, reached the 3.0 milestone today. In this release, Respawn now supports complex circular/cyclical relationships. When Respawn detects a cycle in the graph, it substitutes a separate deletion strategy by disabling/enabling foreign key constraints just for those tables affected. This release also adds

Microservices

Designing Microservice Messages: A Primer

When you move from monoliths to microservices, and your services aren't 100% isolated from each other, eventually you need your microservices to communicate. They need to expose their capabilities to other applications and systems, and when you get to this point, you need to design their means of

Agile

The Gemba Walk for Designing Software

The Gemba Walk is a common lean practice for understanding a current process as-is before taking any action to improve that process. Traditionally, you'd see this in lean manufacturing, where you'd walk through a process, in-person, to understand the purpose, process, and people involved

OSS

Respawn 2.0 released

A small release for Respawn but there's a breaking change in the underlying extension API, hence the major version bump. A couple things added here: * Support for MySQL * Support for Amazon RDS (from a bug fixed) The API change was added so that database adapters can specify the

Agile

Trunk-Based Development or Pull Requests - Why Not Both?

Trunk-Based Development movement is often proposed as the alternative to Git Flow. I understand this distinction - managing streams of work through long-lived branches can be trouble. For those new to TBD, it can look like this means throwing away all branches and everyone commits literally to trunk. Typically

OSS

MediatR 4.0 Released

The last major release of MediatR brought a simplification in design. Instead of having several different IRequest types and IRequestHandler implementations with several flavors, MediatR would try at runtime to determine how a single IRequest should resolve to different IRequestHandler implementations (synchronous, async, async with a cancellation token). In practice,

AutoMapper

AutoMapper 6.2.1 Released

Release notes here. The previous release introduced some inadvertent breaking behavior changes in convention-based map creation and some DI scenarios. This maintenance release fixes these two issues by: * Allowing configuration of member lists to validate per-map * Allowing resetting of static mapper configuration (for testing scenarios) Find this release

OSS

AutoMapper extensions for Microsoft DI 3.2.0 released

Today I pushed out a small change to the AutoMapper.Extensions.Microsoft.DependencyInjection package to allow instance-based initialization. Before you initialize with services.AddAutoMapper(), set a configuration flag: ServiceCollectionExtensions.UseStaticRegistration = false; services.AddAutoMapper(); By default the extension will register using Mapper.Initialize, but with this flag off, the extension

OSS

AutoMapper 6.2.0 Released

Today I pushed out AutoMapper 6.2.0. Check out the release notes for the closed issues. A couple of big features in this release include inline maps, where AutoMapper no longer requires you to call CreateMap for new maps. I had resisted this idea (and even took out the

Microservices

Composite UIs for Microservices - Data Composition

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In the last post, we looked at composing at the server side, both through composing through widgets/components, and then for data sources for a widget themselves, using model composition to pull data from multiple sources

Testing

Respawn vs SQL Server Snapshots

One of the newer features of SQL Server is the ability to snapshot a database at a point in time, and restore it. A commenter on the Respawn announcement asked if I had looked at this feature for resetting a test database to a known point. I hadn't,

Microservices

Composite UIs for Microservices - Server Composition

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In the last post, we looked at techniques for composing on the client side. One of the issues we saw is there aren't really a lot of tools to perform composition, nor are there

OSS

Bulk Writer 1.0.1 released

A few years back, I had a somewhat new problem on hand. I needed to, on a daily basis, wipe and re-insert about 100 million rows of product data into a customer support database. The data was in the form of a single CSV file (zipped of course), and

Testing

Respawn 1.0.0 released

Respawn is a small library to help reset your database to a known state before tests. If you're like our teams and rely on integration/subcutaneous tests as your final "green" test for feature complete, keeping a consistent database state can be frustrating. Respawn solves this

Microservices

Composite UIs for Microservices - Client Composition

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In the last post, we looked at possible areas of composition: * Client * Server * Database In this post, we'll look at compositional options in the browser. From the outset, I can at least confirm that

AutoMapper joins the .NET Foundation

Today marks a new era for the AutoMapper project, as we join the .NET Foundation. There were a number of reasons I wanted AutoMapper, from the legal to continuity. I'm going to steal Peachpie's announcement a bit for the benefits: * As a contributor: When you make

Microservices

Composite UIs for Microservices - Composition options

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition In our previous post, we looked at why we might compose, seeing it's primarily an edge concern, where we're exposing our services to end users. Those end users could be customers, or

Microservices

Composite UIs for Microservices - A Primer

Posts in this series: * A primer * Composition options * Client composition * Server composition * Data composition Microservices can be easy, if we never have to compose, orchestrate, or otherwise integrate between multiple services. If our inter-service communication is low, we can piecemeal a solution based on basic integration patterns such as

AutoMapper 6.1.0 released

See the release notes: v6.1.0 As with all of our dot releases, the 6.0 release broke some APIs, and the dot release added a number of new features. The big features for 6.1.0 include those for reverse-mapping support. First, we detect cycles in mapping