Composite UIs for Microservices - Client Composition

Posts in this series: A primer Composition options Client 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 browser-side composition: Does not require you to use a SPA framework SPA frameworks generally do not have compositional tools built in I've yet to see a [Read More]

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 a contribution to the source code of the project, you will sign a CLA based on an automated mechanism the .NET Foundation will set [Read More]

Composite UIs for Microservices - Composition options

Posts in this series: A primer Composition options Client 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 they could be internal business users, anyone really. Once we see that we need to compose, the next logical step is to determine how we should compose. But [Read More]

Composite UIs for Microservices - A Primer

Posts in this series: A primer Composition options Client 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 messaging. A land without composition and integration is when I have highly decoupled systems and business organization. If I strictly build systems around the organization [Read More]

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 classes to automatically preserve references. Much larger however is unflattening. For reverse mapping, we can now unflatten into a richer model: [Read More]