Systems | Development | Analytics | API | Testing

Welcome to the final entry in Yellowfin Japan’s long-running ‘How to?’ blog series! This series of blogs has aimed to to provide your team with a step-by-step guide of how to create your own Yellowfin dashboard, starting from the design and data transformation flow, all the way to creating rich data visualizations and using the right report filters.

Background tasks are one of the core pillars when considering web applications for scale. The basic idea is simple: A client makes a request to your web application and in handling that request, your app performs several time-expensive tasks. To allow it to respond to the client faster, the app enqueues a background job to a background processing system. The background processing is then tasked with all the heavy lifting, like computations or I/O operations.

This article was originally published on The New Stack on Dec. 19, 2024. Imagine driving a car with a headset that only updates your view every five minutes instead of providing a continuous video stream. How long would it take before you crashed? While this type of batch processing clearly doesn’t work in the real world, it's how many systems operate today. Batch processing, born out of outdated technology constraints, forces applications to rely on static, delayed data.

Ensuring secure access to applications and APIs is critical. As organizations increasingly adopt microservices architectures and cloud native solutions, the need for robust, fine-grained access control mechanisms becomes paramount. This is where the combination of Open Policy Agent (OPA) and Kong Gateway shines.

Software Testing is the most important step in the software development process. This process helps in validating and verifying that a software application is Bug-free, and the software is improved in terms of efficiency, accuracy and usability. Black Box Testing and White Box Testing are two most useful testing techniques for Software Testing. In this blog, we will be covering more about their definitions, advantages, disadvantages, their types, limitations and tools used for testing.

Marketers at financial services companies have their work cut out for them. Their companies have a wealth of data, but that data is often fragmented among different systems and divisions, and protected-class data has a wide range of restrictions on how it can be used for different product lines.

The GUI is the very first thing users see when they interact with your web/application. To do GUI testing is to craft the best first impression for your users. You can do GUI testing either manually or automatically. Automated GUI testing significantly reduces the risk of false positives. In this article, we’ll explore the concept of GUI testing, why it’s important, and GUI testing best practices.

Test automation is no longer a luxury; it’s a necessity. But beneath the promise of faster releases and streamlined testing lies a reality few anticipate: automation isn’t a set-it-and-forget-it solution. Beneath the surface, test maintenance poses some hefty hidden costs. If not handled well, these costs can snowball, derailing both budgets and timelines.

Let’s talk about stubbing and verifying – two critical tools that transformed how I approach testing. Early in my career, testing was often frustrating, slow, and full of surprises, most of them bad. I used to think testing meant running my app against real systems and crossing my fingers that everything worked. Spoiler: it rarely did. Here’s the thing: testing doesn’t have to be painful.