When you are responsible for the delivery and maintenance of critical or complex applications built on cloud infrastructure, the chances are you are relying on multiple in house engineers or teams of engineers, devops and external consultants to keep your network and applications operating at peak performance for your end users.

Software development can be a long and complex process. The more you can map out and plan, the greater chance you have of success.

When moving your data and applications to AWS or developing a solution from scratch, you are most likely going to be faced with the challenge of selecting the most appropriate of the multitude of database options offered by AWS.

If you used Arcentry in the past to document your cloud infrastructure, the closure of the service earlier this year probably came as a bit of a shock.

While quite a newcomer having only been established in 2018, the decision to shut the doors at short notice potentially left a lot of people high and dry that were using the service to diagram their cloud infrastructure. 

The AWS Well-Architected Framework provides guidance on applying best practices in the design, delivery and maintenance of AWS environments.

Tags are an incredibly useful yet often overlooked feature of most cloud computing platforms. Once created they let you manage your infrastructure more effectively by providing the ability to filter resources and perform tasks and actions based on nominated tag values.

No one needs network documentation, until they do. 

The best and most perfect cloud architecture is next to useless if no one in your organisation understands it. What maybe even worse is if everyone misunderstands it, which is why we believe accurate documentation is an essential step in network architecture design and implementation.

In the world of flow charts and mind maps, Lucidchart has gained a strong following and undoubtedly has proven itself a worthy adversary to the likes of Visio, draw.io and Xmind.