Systems | Development | Analytics | API | Testing

At WSO2, our company culture is the heartbeat of everything we do-rooted in honesty, transparency, and inclusivity. It extends beyond our walls, driving our mission to revolutionize digital experiences through cutting-edge solutions and a customer-centric ethos. We believe this is why WSO2 continues to earn the confidence of organizations worldwide.

In software testing or platform engineering, having realistic data is crucial. For years, teams have relied on Test Data Management (TDM) to copy entire production databases, scrub any sensitive information, and then spin up test environments from these sanitized data sets. While TDM gets the job done, it can be costly, time-consuming, and can quickly become outdated. The issue of outdated data becomes more pronounced as deployment velocity increases and back end dependencies become more diverse (think: microservices).

In the half-decade since gRPC became part of our production ecosystem, we've encountered a range of challenges and discovered a few hidden pitfalls that can trip up even the most experienced teams. Below, we'll walk through some of the core lessons learned, with tips, best practices, and examples drawn straight from the trenches.

Traditional testing methods often delay the software development lifecycle, as we have grown used to these outdated processes without considering alternatives. Ephemeral environments introduce a more efficient solution. They allow for the quick creation and dismantling of isolated testing environments. These isolated environments approach leads to faster and more productive development cycles while still delivering high-quality software to users. In this article, we'll explore ephemeral environments, how they work, and why they might be the solution your team needs.

In almost all industries, a standard set of KPIs helps to guide teams on whether they are doing the right things in the right ways, with the right outcomes. In software development, this is something that can sometimes go untouched, allowing ourselves and fellow developers to continually work on our code and platforms without making sure we are paying attention to what matters. Some development frameworks, such as Agile, have some KPIs baked directly into them. For example, when calculating your team's story point velocity, you likely establish a benchmark after a few sprints, which becomes a team KPI to meet or exceed.

Service virtualization is increasingly popular in the software & DevOps toolkit. Learn what it is, how it works, and how to use it. Service virtualization is an increasingly popular tool in the software developer and DevOps toolkit. This blog covers what it is, its use cases, and how it works. This introduction is part of our in-depth series on service virtualization. Stay tuned and follow along for more content!

Mock APIs are vital tools in modern software development. They allow developers to simulate APIs and continue testing and development without backend dependencies. This guide covers how mocking toolsets enhance efficiency and ensure rigorous testing, streamlining debugging and feature integration for increased productivity and innovation.

Testing AWS services is an essential step in creating robust cloud applications. However, directly interacting with AWS during testing can be complicated, time-consuming, and expensive. The AWS SDK Mock is a JavaScript library designed to simplify this process by allowing developers to mock AWS SDK methods, making it easier to simulate AWS service interactions in a controlled environment. Primarily used with AWS SDK v2, AWS SDK Mock integrates with Sinon.js to mock AWS services like S3, SNS, and DynamoDB.