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
NoSQL on AWS: Document-Oriented Databases
A document-oriented database stores keys mapped to JSON documents. You can query all documents in such a document-oriented database and retrieve only parts of documents to save network bandwidth.
continue reading
10 Obstacles for Lift & Shift Architectures
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
Part II: Generating Live Cloudcraft Architecture Diagrams in Confluence
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
Storage on AWS
How do you choose the best storage option on AWS?
Choosing storage service is critical when designing a cloud architecture. Read on to learn about the characteristics, limitations, typical use cases, and a decision tree for the following options to store data on AWS:
continue reading
Messaging on AWS
Previously, I compared all database options offered by AWS for you. In this post, I compare the available messaging options. The goal of messaging on AWS is to decouple the producers of messages from consumers.
The messaging pattern allows us to process the messages asynchronously. This has several advantages. You can roll out a new version of consumers of messages while the producers can continue to send new messages at full speed. You can also scale the consumers independently from the producers. You get some kind of buffer in your system that can absorb spikes without overloading it.
In this blog post, I introduce all the messaging options that AWS offers. Afterward, I end with a comparison table of the options.
continue reading