At Container Solutions, one of our ‘bread and butter’ engagements is to help a software infrastructure team move from more traditional software delivery paradigms to Cloud Native ones.
Other Posts Part I Part II Simple Filters In this section we introduce the most-frequently used feature of jq: the filter. Filters allow you to reduce a given stream of JSON to another smaller, more r...
As Cloud Native consultants, we often get asked about managing cloud costs. The business that doesn’t ever want to save money is a rare one indeed. However, what we have found is that in the Zero Inte...
Introduction See Part I to get an introduction to this series, and a guide on the Hard Way method. In this post, we cover: What jq is Look at examples of it Introduce key terms Briefly look at its pla...
The history (and prehistory) of Cloud Native has been characterised by the gradual encroachment of automation on more and more pieces of the software engineering lifecycle. In the dark ages before the...
Introduction At Container Solutions, we spend a significant amount of engineering time wrangling JSON requests and responses to and from various APIs. While traditional text-processing tools such as g...
Previously, we’ve written about how money flows across your business ultimately determines your operating culture, with posts on how transforming IT starts with finance, and how agility is related to ...
Recently an Amazon Prime Video (APV) article about their move from serverless tools to ECS and EC2 did the rounds on all the tech socials. A lot of noise was made about it, initially because it was in...
