The promises of adopting the cloud for your software are enticing. Effectively limitless scalability, large reductions in capital expenditure, efficiency savings in staffing through automation. An exciting prospective, and one that…
-
-
When approaching development of Microservices, it’s often easy to think of the services themselves as the valuable pieces of your system. each service you add gives you more functionality, and…
-
The Original DRY, WET and Slogan Based Development Hopefully, you now understand some of my pain when I’m arguing against DRY, and arguing against deep abstractions. The original definition of…
-
My good friend Peter Ledbrook has been pondering the question how can we share code between microservices This is something we’ve had the opportunity to experiment with, on new projects…
-
Don’t Repeat Anything == The Tower of Coupling Copy and Paste, it’s bad. We have this drilled into us as received knowledge. We must build abstractions to avoid copying code,…
-
I recently had a thought provoking exchange on Twitter with Luke Daley who is a Gradle developer, creator of the Ratpack web framework and all around awesome fellow. We were…
-
All Hail the Command Object This is a follow on to Simplicity in Web Architecture – Beware the Stateless Service In that article, I gave my opinion on the Stateless…
-
This is a response to a blog post by Peter Ledbrook on his blog In it he asks about the future of Grails (and links to a recent talk of…
-
Simplicity in Web Architecture – Beware the Stateless Service This article is related to my recent talk at the London Groovy/ Grails User Group which you can see at SkillsMatter…