Amazon Web Services is always changing. New features are added and new services are launched all the time. But during re:Invent – the annual AWS conference – a flood of news is poured out on us. Some news will change the way we architect cloud-native applications today or in the coming months. While other news is irrelevant to us.
Fighting climate change is one of the biggest challenges of our days. When designing an architecture, there are many important factors to consider: security, reliability, performance and costs. I’d like to add another factor to that list: the CO² footprint.continue reading
AWS provides many building blocks. As architects, we have to choose the right building blocks to construct our systems. But sometimes, the proper building block is not available, and we have to make compromises. In this blog post, I show four unusual AWS architectures that deal with AWS’s limitations in creative ways.continue reading
Oftentimes, the idea of adding a caching layer arises when users start complaining about the performance of an application. Adding a cache to your architecture does not solve all problems — especially when implementing that change under pressure to fix performance issues. Therefore, thinking about a caching strategy should be part of the process when designing your architecture.continue reading
The cloud is not only about greenfield projects. Over the last few years I have accompanied several enterprises in large migration projects from on-premises to the Amazon Web Services (AWS). This blog post gives an overview of typical obstacles for lift & shift architectures and points out possible solutions.continue reading
Welcome to Part 2 of the Cloudcraft API series! If you haven’t configured Postman and Cloudcraft yet, check out Part 1.
The goal of this part is to:
- Use Cloudcraft’s API to make a request to update your existing blueprint
- Apply AWS tagging best practices for filtered snapshots
- Embed your live blueprint into Confluence for your change management or documentation workflow