As the world of technology continues to progress, so are the technologies that developers work with on the daily. Whether it’s cloud native, Kubernetes, serverless, or distributed architectures, every developer team has encountered the difficulties of working with them. Even more so, they’ve felt the challenges associated with trying to find the solutions to those same difficulties. But what if it was as easy as opening a book?

ISO 25010 helps you to ensure that your software is high quality. Read along or jump ahead to the section that interests you the most.

Testing in production simply means testing new code changes in production, with live traffic, in order to test the system’s reliability, resiliency, and stability. It helps teams solve bugs and other issues faster, as well as effectively analyze the performance of newly released changes. Its overall purpose is to expose problems that can’t be identified in non-production environments for reasons that may include not being able to mimic the concurrency, load, or user behavior.

As COVID-19 vaccinations continue to roll out, organizations across industries prepare to return employees to the workplace. It’s a journey fraught with anxieties, uncertainty, and unknowns. In a recent poll of Appian webinar participants, a mere 17% reported that their companies feel fully prepared to reopen facilities, and only 51% said they felt even “somewhat” prepared. The good news is that a safe return to the workplace is not uncharted territory.

MongoDB and MySQL are similar is some ways, but they also have some obvious differences. Perhaps the most obvious one is that MongoDB is a NoSQL database, while MySQL only responds to commands written in SQL. Potential users may want to examine MongoDB vs. MySQL in the areas of performance and speed. The following article will help you understand the differences, as well as the pros and cons of each database.

In this article, I will be focusing on the contribution that a multi-cloud strategy has towards these value drivers, and address a question that I regularly get from clients: Is there a quantifiable benefit to a multi-cloud deployment? That question is typically being asked when I explain the ability to leverage container technology that offers a consistent deployment environment across multiple clouds and form factors (public, private, or hybrid cloud).

TL;DR: Yes, you can do it. And no, you don’t need a separate tool for it. “Reverse ETL” is a fairly recent addition to the data engineer’s dictionary. While you can read articles upon articles about it (there’s a pretty good ‘primer’ in the Memory Leak blog), it can be summarized as being the art and science of taking data from your data warehouse and sending it somewhere other than BI - generally into other tools and systems where it becomes operational.

With the ever-increasing demand to deploy high quality and reliable software faster, automation has become an integral part of modern software development. By seamlessly integrating your existing test automation efforts with Zephyr Scale, you can benefit from faster releases, tighter collaboration, and better visibility of your testing processes. Read on to discover why and how you can unify test management and automation in a single tool with Zephyr Scale.

When we write scripts for one browser, they may not necessarily run on all browsers. It’s a no-brainer. And, we all know that a few browsers can limit certain features. For instance, if we design features that run on Safari on Mac OS, those features may not function across other browsers. To ensure the features run uniformly across various browsers and OS versions that our users have, we should perform multi-browser testing.

Measuring and offsetting your carbon footprint may seem like a daunting task. In this post, we’ll explain how to easily and quickly perform the calculations in a DIY style. Let’s go!