Recently, I had the pleasure of attending the 2018 DevOps Enterprise Summit (DOES) in Las Vegas. While conferences tend to make me fearful of getting sucked into a big sales show, DOES restored my faith (in the value of conferences, not Vegas!). Notably, it was extremely well-attended, impeccably run, and there was an elite cast of speakers throughout the event. From large talks to small group sessions to book signings, the event offered seemingly endless opportunities for interactive education.
Keeping applications up-to-date is important. It allows you to take advantage of the latest framework/component features as they are released, run on the latest devices/platforms, and provide the best user experience possible. Upgrading from one version to the next is usually easier than jumping two or more versions ahead. For these reasons, regular application maintenance to upgrade frameworks and components as they come out is the preferred approach.
One of the foundational steps in moving to DevOps is application monitoring, which is not always easy. There are many different possible performance problems and limitations, and the only way to track them down is by collecting information in bulk. Ask any developer who has maintained an application without the proper monitoring tools, and you'll probably hear a story or two about some issue that took months to track down or is still plaguing the application. Developers, server admins, and network engineers need information to be able to track down a problem.
In this article, I walk through an example of how application performance monitoring can help quickly discover, isolate, and solve problems that can negatively impact the user experience.
Imagine you’re having issues with a third-party service that is called whenever a user logs in. Occasionally, the service is unexpectedly unavailable, leaving users stranded when they wanted to sign in to make a purchase. This happens about once a month, resulting in frustrated customers and some scrambling by the dev team before finding the issue.
Making calls to a third-party application is outside the realm of CloudWatch’s abilities, but there is a way to leverage AWS to combat this issue by taking advantage of the cloud’s monitoring capabilities. In this article, Senior Developer Zachary Sersland walks you through an AWS .Net Lambda function example that will prevent your third-party authentication service from becoming unavailable.
In the quest for digital transformation, containers aid in increasing the portability and rapid delivery of applications. They are a tool that fits perfectly within the Cloud, Agile, DevOps toolkit. The catch is, the decision to try containerization involves getting buy-in from multiple groups of people.