Introduction

If you’ve read the first two posts in this series, welcome back. So far in our story, our heroes – microservices and serverless functions – save us from a monolithic meltdown. Go have a read if you’d like to laugh, cringe, and learn from my adventures.

This final post covers a different project. We had...

Platform Management

In our previous article (The Shift to PaaS), we talked about the “subscribe and go” model for platform consumption which is increasingly enabling mainstream adoption of cloud-native platforms. However, this model may not suit all business requirements and many organisations must deal with a...

Platform Subscription

As cloud-native platform technologies mature and become mainstream, the type of organisations utilising these platforms changes. There is less emphasis on install and operate and more of a shift towards optimisation and realising business benefits. Early adopters are done “experimenting” with...

Introduction

If you’ve read part one of this series, welcome back. If you didn’t, it was an action-packed exposé on start-up life and the ways in which microservices will decrease your stress and your snack budget. Pour your beverage of choice and go read it.

In chapter two - the project hits the big-time. Serverless 

When customer reach and innovation is at an all-time high, the ability to respond with speed, agility and quality are paramount. Gone are the days where months are spent figuring out how to build a more secure application development and delivery platform that serves the changing needs of business whilst also ...

Introduction

In the early days of my career, monolithic APIs were common. SOAP and XML were still popular - REST and JSON were the new kids on the block.

I worked in a development team that had inherited a monolithic API. A bad deployment left multiple key systems inoperable, and our support lines were inundated to...

When Deloitte Platform Engineering teams start on a new client, we bring with us our development processes that help deliver value.

These processes continuously improve as they are applied to many, many engagements and evolve as trends and industry consensus change. This means that we can have all the maturity that...

Introduction

In the previous post of the series, we described the design of an approach to meet common observability requirements of distributed services using Azure Functions. Now, in this post, we are going to cover how this can be implemented and how we can query and analyse the produced tracing logs.

This post...

With the constant evolution of governance, compliance and security, it can be a daunting prospect to balance best practices while promoting lean and efficient delivery approaches.

In this post, we will walk through and demonstrate how using best practices pipeline structures, standardisation, and cross-team...

Introduction

In my previous post, I discussed why it is important to consider traceability and observability practices when we are designing distributed services, particularly when these are executed in the background with no user interaction. I also covered common requirements from an operations team supporting...