Smart contracts offer a unique way to solve business problems but also present a unique challenge when it comes to managing the rollout of new and updated smart contract based applications. The ‘Accept-Then-Publish’ approach described below is a way to manage this complexity. …

The aim the Fluid Manifesto is to promote a set of techniques and approaches that allow web services to be continuously updated. Fluid Messaging describes how a similar approach can be used when working with asynchronous messaging systems. Approach As a publisher we want to be able to start publishing an…

Imagine deploying your latest web service version to production unencumbered by the payload structures currently in use by the community. The aim the Fluid Manifesto is to promote a set of techniques and approaches that allow exactly that. …

Fluid schema evolution is a way to manage the evolution of JSON payloads in a web service or messaging context. Fluid schema evolution works by detecting changes to the JSON schema; snapshotting and versioning schema metadata; then generating migration scripts for the contexts in which the changed objects are used…

A model for running projects where the software is developed externally to the sponsor company but operated and maintained internally. Premise Large corporations with big software development budgets like to run and control projects themselves choosing the best software developers. …

On at least one occasion I’ve had to explain why at-least-once is the preferred if, not only, choice of message processing for most scenarios. …

An approach to building web services that allows the services to continually evolve with graceful fallbacks. Manifesto A fluid web service is one that will evolve as needed to be the best representation of the service provided. A consequence of this approach is that the service can change at any moment…

An approach to software versioning that does away with manual versioning, unnecessary check-ins or dependency on environmental variables. It is mainly of use inside agile project teams set up to continuously deliver value (for example releasing on a weekly basis). …

A common library dependency pattern that works well for medium sized teams. Preface This article describes how we get into dependency hell and how using a composite uber commons library improves things. One aspect of dependency hell is where making a dependency change results in a conflict in transitive dependencies. Sometimes…