As software ages, eventually and inevitably, it’s going to become out of date and misaligned with organizational goals and objectives. Here are four steps for determining the health of your legacy applications and whether or not they are ready for modernization or retirement.
Charity Majors, co-author of Database Reliability Engineering, shared a tweet that drives home how to approach the transition from single applications to a complex, distributed system of microservices.
@mipsytipsy. “Embrace the fact that everything is failing all the time - and it’s okay! We build for resiliency, not uptime.” Charity Majors, Twitter, https://twitter.com/mipsytipsy/status/1134499865335963648.
You can invest a lot in making any single system component reliable, performant, and scalable. The investment is often worthwhile and necessary, but what matters to users is the system’s uptime as a whole. Reliable components aren’t enough to make the entire system reliable if it’s unable to tolerate and recover from failures. Here are some thoughts about building your system for resiliency and two popular microservices patterns to cope with failure.
We’ve all seen charts of the software development lifecycle (SDLC). They often have a stage with a name such as “operate” or “maintain” that the development team will briefly mention in their enthusiasm to move on to the next stage: building new features. But the operational phase of the software development lifecycle is, in many ways, the most important; it’s where the rubber meets the road.
By making operability a priority for your software, you’re investing in a maintainable present and the data to build the future. Here are four steps effective software development teams take to ensure they get the operational phase right.
Forbes Technology Council Is an Invitation-Only Community for World-Class CIOs, CTOs, and Technology Executives.
Chicago, IL, October 2, 2019 - Patrick Emmons, CEO and Founder of DragonSpears, a custom software development company, has been accepted into Forbes Technology Council, an invitation-only community for world-class CIOs, CTOs, and technology executives.
One of the biggest fears of any product owner is opening your website one morning and finding nothing there. Your site has disappeared without a trace, and you’re left scrambling to pick up the pieces. Fortunately, one of the many benefits of having your application live in the cloud is the ease with which your data can be backed up.
AWS offers reliable backup services for many of its resources. Here are some effective strategies for backing up data in Amazon’s RDS, EBS, S3, and AMI. By implementing these procedures, your worst nightmare becomes only a temporary setback!