Ben Morris. Agile enterprise architecture.

[...] order that they were sent. This is not a guarantee that any queuing system can provide and Azure Service Bus is no exception. At the heart of this is the fact that the network is not reliable. Message [...]

[...] If you want to create a serviceable messaging client for Azure Service Bus then you will need to put some basic scaffolding in place for controlling latency and [...]

[...] set of methods that make it easy to start sending and receiving messages through the Azure Service Bus. The problem is that it doesn’t do much to provide some of the basic scaffolding [...]

[...] a basic set of methods that make it easy to start sending and receiving messages through the Azure Service Bus. The problem is that it doesn’t do much to provide some of the basic scaffolding [...]

[...] The Entity Framework has come a long way since its earliest incarnations prompted a vote of no confidence from [...]

[...] A generic repository is often used with the entity framework to speed up the process of creating a data layer. In most cases this is a generalization too [...]

[...] A generic repository is often used with the entity framework to speed up the process of creating a data layer. In most cases this is a generalization too [...]

[...] closely coupled to the IQueryable<T> interface. Typically, data is accessed via the entity framework or a similar collection that implements the interface. This creates a “magic box” where [...]

[...] . It’s left to the services themselves to find solutions to these problems. For example, fault tolerance and buffering can be provided by adding low-latency messaging behind the service end-point. [...]

[...] tolerance from a service that is tightly defined using a detailed format such as WSDL. Fault tolerance and REST REST and HTTP APIs provide more scope for version tolerance as they are not governed [...]

[...] in queries where both the request and response are generally transient and short-lived. The fault tolerance and resilience that you’d expect to derive from messaging is also compromised in query [...]

[...] approach based on event messaging would be a more effective means of eliminating temporal coupling. Event messaging will allow information to be broadcast without any expectations over who [...]

[...] scenario. Given that a request always expects a timely response a query inevitably adds temporal coupling to a system where the consumer depends on a response to complete an operation. This is not [...]

[...] compatible with having to guarantee the order in which events are processed. This creates temporal coupling between components so the integration resembles a stream of web service calls rather than a [...]

[...] . Some people even advocate avoiding the issue altogether and adopting techniques such as tolerant readers to allow for loosely defined and flexible contracts. That involves opening a wholly [...]

[...] to use the same version of a schema. In a sense, your consumers automatically become tolerant readers that only choke on a payload if it is missing specific information that they are expecting. [...]

[...] as once you break this dependence on schema versions you can never sure whether your tolerant readers are about to start failing. One way to close this information gap could be to require [...]

Agile principals encourage self-organising teams to take ownership of development. Does this mean that they choose their own development tools and tec [...]

[...] moment” can help you to adapt to the inevitable uncertainty that comes with agile development. The risk is that it can become an excuse for uncertainty that undermines development [...]

Agile principals encourage self-organising teams to take ownership of solutions. This doesn’t leave architects out in the cold, but it does require [...]

[...] If you want to create a serviceable messaging client for Azure Service Bus then you will need to put some basic scaffolding in place for [...]

[...] is that it doesn’t do much to provide some of the basic scaffolding required by a serviceable messaging client. [...]

[...] that it doesn’t do much to provide some of the basic scaffolding required by a serviceable messaging client. [...]

[...] create a serviceable messaging client for Azure Service Bus then you will need to put some basic scaffolding in place for controlling latency and temporary error conditions. [...]

[...] through the Azure Service Bus. The problem is that it doesn’t do much to provide some of the basic scaffolding required by a serviceable messaging client. [...]

[...] the Azure Service Bus. The problem is that it doesn’t do much to provide some of the basic scaffolding required by a serviceable messaging client. [...]