Operations | Monitoring | ITSM | DevOps | Cloud



This year's major trends in cloud migration

It is no secret that companies are shifting large infrastructures to the cloud. With more and more companies undergoing the digital transformation of their services, we have been witnessing cloud adoption as a software growth and maintenance strategy for a few years now. The nature of this movement has changed over time, so it is important to ask yourself what cloud adoption looks like today.


How integrating AWS into Cortex augments visibility into your infrastructure

With AWS re:Invent right around the corner, infrastructure has been top of mind at Cortex. Earlier this year, we launched our revolutionary Resource Catalog, which integrates with AWS accounts to automatically ingest all infrastructure components, from s3 buckets to lambdas. Through this process, Cortex allows you to track everything in a single place, while augmenting the information that already exists in AWS. The Resource Catalog surfaces live information about your infrastructure assets.


Effective vulnerability management for your microservices

Vulnerabilities are part and parcel of the software development life cycle. If left untreated, they can expose your application to malicious attacks, which can be detrimental to its functioning and reliability. To avoid severe damage and complications that arise from having the vulnerabilities exposed, it is good practice to set up a vulnerability management system.


Mapping service vulnerabilities with Mend

Mend is an automated vulnerability scanning tool that helps teams detect and resolve issues quickly. Mend can discover outdated packages and tell you if you’re relying on tools with known issues. Then, through automated remediation, Mend creates pull requests for developers with specific guidance on resolving those issues. Mend conducts static code analysis as well as package and dependency management analysis to identify weaknesses.


The underappreciated power of technical project managers

Imagine you’re part of a software development team that’s working on an important new project. Everyone is excited about the work, but you’re running into trouble. The work wasn’t clearly divided up, so some of the engineers unintentionally did overlapping work. Meanwhile, neither the PM nor the engineers realized that they would eventually need sign-off from an external stakeholder, who doesn’t agree with all of the project requirements.


Visualizing GraphQL Traces in Microservices

One of the things that most excites me about what we at Helios are doing differently than anyone else is trace visualizations. While there are many ways to troubleshoot microservice architectures, a good visual overview goes a really long way to speeding up understanding and therefore accelerating time to a resolution. When your manager asks, “Why did that break down?” with Helios you can answer quickly with accurate data—this is the value of the Helios platform.


How reporting enables informed decision-making

For software development teams to make meaningful progress, they must invest in efficient monitoring, reporting practices, and tooling. This is because only by keeping track of select metrics, such as those pertaining to application performance, will you know whether you are on the right track. Without knowledge of whether the software is functioning and performing as it is supposed to, there is no way of knowing what, if any, changes need to be made.


Picking the right developer workflow tools for your team

The software development life cycle is by no means a short or easy process. From project design to post-production monitoring, each stage of the life cycle comes with its own set of workflow-related demands. Teams must develop adaptable yet agile workflows to prioritize efficiency while simultaneously ensuring a positive developer experience. Thankfully, there is no shortage of tools to boost productivity in software development team workflows.

Sponsored Post

Introduction to Automation Testing Strategies For Microservices

Microservices are distributed applications deployed in different environments and could be developed in different programming languages having different databases with too many internal and external communications. A microservice architecture is dependent on multiple interdependent applications for its end-to-end functionalities. This complex microservices architecture requires a systematic testing strategy to ensure end-to-end (E2E) testing for any given use case. In this blog, we will discuss some of the most adopted automation testing strategies for microservices and to do that we will use the testing triangle approach.