APIs

In this post, I show how I use GitHub Actions to call an Azure Function (through Azure API Management) that interacts with Google Analytics as part of the process to build my Hugo Static Site. The end result is that top posts are pulled into the Static Site Generation build process, rather than calling the Google Analytics API through JavaScript at runtime.

In this talk, Asanka will introduce the ‘cell-based’ reference architecture, which is decentralized, API-centric, cloud-native and microservices friendly. He will explain the role of APIs in the cell-based approach, as well as examine how real applications are built as cells. Asanka will explore the metrics and approaches that can be used to measure the effectiveness of the architecture and explore how organizations can implement the cell approach.

Back in June, I wrote a blog post on API Management and how you can use API Management policies to enforce access restriction policies. I was going to write a follow up post on how to use API Management policies in additional scenarios, but it’s one of those scenarios where great minds think alike!

There are so many types of data stores out there these days. You have relational, non-relational, documents, blob, tables, files and more. There’s also a growing awareness of ‘Polyglot Persistence’ where you use different data stores depending on the task. But how do you know which is the ‘right’ one? Chris is joined once again by Steph Martin as we talk through some of these types of datastores, and the factors that may help you in your decision!

We recently introduced you to API Management, how it maps to architectural principals and why you may consider using it as a producer or consumer of APIs. In this post, we’ll be continuing on the story - focusing mostly on the API Management policies functionality.

We now live in a world where multiple systems connect or integrate with each other. This is not new, and has been a technology trend for some time. But - in a world of distributed compute (on the increase, thanks to cloud), and the rise of microservices, we find that we have more and more services that we need to integrate with each other. Integration is typically handled through a couple of routes, including Enterprise Messaging (such as message brokers), as well as APIs (Application Programming Interface). There are many areas that we should consider when building our APIs, and that’s what we’ll give some thought to in this blog post.

We’ve previously covered the theory of the Geode pattern in episode 11. Now it’s time to see it unfold live and in action! Tune in to see Will demonstrate the concept of the Geode pattern and how it adds value to a globally distributed application.

How often do you think about the configuration of your applications across environments/regions/deployment boundaries? What if that configuration was stored somewhere externally but centralised, to make management easier? That’s the idea behind the external config pattern! How about another scenario - What about those times where you’ve wanted to use a messaging service, but your payload is too big? Thought about externalising that payload too? Well, that’s the Claim-check pattern! Join Peter and Chris as they talk about both of these patterns in this episode of Cloud with Chris!

Have a need to update a legacy application to use cloud concepts such as retry, circuit breaker or other features? Then the ambassador or sidecar patterns may be for you! Join Peter and Chris as they continue their journey exploring Cloud Design Patterns. In this session, they discuss the Sidecar and Ambassador Patterns.

Heard about something called a Landing Zone, and think you need a helicopter ready to use it? Not quite! In this session, Chris is joined by Karim Fahmy as they discuss an introduction to Azure Landing Zones and how they underpin some of the core cloud foundations (e.g. governance, networking, core infrastructure and more) to enable a successful cloud deployment