"Don't overengineer this. We need to move as fast as we can."Too many business representatives The Agile Manifesto is built on 12 pillars, the 9th of which (at the time of writing) is: Continuous attention to technical excellence and good design enhances agility. I regard the Agile Manifesto as a thing of truth. It has … Continue reading Technical Excellence
Category: Coding
Microservices with AWS Lambda
I've been building microservices for several years. I've mostly used DotNet, DotNet Core, and Ruby on Rails to build them, and I've generally deployed them either into AWS EC2, or Azure Service Fabric. I've found most enterprises aren't ready for managing microservices in containers, either in the cloud or their own data centres. Keeping things … Continue reading Microservices with AWS Lambda
Conway’s Shackles?
Does Conway's Law have a dark side?
Testing Times
A dive into the many different ways developers can and should test.
A Refreshing Change
Data refreshes are not the answer.
Where Patterns go to Die
An essay on why software patterns become anti-patterns and how to avoid pattern rot.
Don’t Stream JSON Data (Part 2)
I've discussed the merits of JSON streaming in two prior posts: Large JSON Responses and Don’t Stream JSON Data, if you haven't read these yet then take a quick look first, they're not long reads. I'm attracted to the highly scalable proposition of scaling out the consumer, so many requests can be made individually rather than returning a … Continue reading Don’t Stream JSON Data (Part 2)
Don’t Stream JSON Data
I recently published a post about how to stream large JSON payloads from a webservice using a chunked response, before reading this post it's probably best to read that post here. Streaming is a fantastic method of sending large amounts of data with only a small memory overhead on the server, but for JSON data … Continue reading Don’t Stream JSON Data
Large JSON Responses
The long slog from a 15 year old legacy monolith system to an agile, microservice based system will almost inevitably include throwing some API's in front of a big old database. Building a cleaner view of the domain allows for some cleaner lines to be drawn between concerns, each with their own service. But inside … Continue reading Large JSON Responses
Getting FitNesse to Work
Sample code here. Recently I've been looking into Specification by Example, which people keep defining to me as BDD done the right way. Specification by Example fully implemented includes the idea of an executable specification. A concept that has led me back to FitNesse having given it the cold shoulder for the last six or seven years. … Continue reading Getting FitNesse to Work
