Systems | Development | Analytics | API | Testing

What Is Spiral Model In Software Engineering?

Would you believe me if I say there is a development methodology that considers changing requirements and technical risks as part of the process instead of obstacles to be overcome? Sounds crazy, right? That’s exactly what I thought about the Spiral Model until I took a closer look. I’m not saying it’s perfect for every project or that we should all use it. But for certain types of projects, the messy, uncertain, high-stakes ones, it may be just what you need!

API Security: Validating Auth and Access with Traffic Simulation Starts with Behavior

Security breaches rarely begin with a hidden zero-day exploit or a complex web of escalated hacks. They often start in very simple ways – an internal team member is breached, a permission is misconfigured, an overly permissive API endpoint is overlooked, or a JWT simply doesn’t expire. An API, or application programming interface, is a set of protocols and tools that enable different software systems to communicate and exchange data, making them essential in modern software development.

A Brief History of APIs

The history of modern technology is a story about APIs. But the same tools that built our connected world have also created complexity and fragmentation. Before we can offload major workloads to AI and autonomous agents, we need to fix the shaky foundation they might be built on. This video explains the evolution of APIs, the challenges of API fragmentation, and why managing the full API lifecycle is critical for the future of tech and artificial intelligence.

ZeroTrust for LLMs: Applying Security Principles Through DreamFactory's Gateway

The key to securing large language models (LLMs) lies in adopting a Zero‑Trust framework. This approach ensures that every interaction - whether from users, devices, or applications - is verified, authenticated, and authorized. With the rise of LLMs in enterprise environments, traditional security models no longer suffice. Here's how DreamFactory's Gateway helps implement Zero‑Trust principles effectively.

What Is A Flaky Test? Causes, Impacts & How To Deal With Them

In software development and automated testing, consistency really matters. One of the most frustrating barriers that developers and QA engineers encounter is a little something we call flaky tests: tests that pass or fail at random times with no changes to the code. These googly eyed tests tend to do the most damage and can produce unreliable results which erodes trust in the testing function and can even cause release cycles to slow down especially in the architectural context of CI/CD pipelines.

Announcing Mesh Manager Support in Konnect Terraform Provider

We’re excited to announce the beta support for Mesh Manager in the Konnect Terraform Provider — a new tool that brings the power of infrastructure-as-code to Kong’s Service Mesh management platform. This provider enables engineering teams to declaratively manage Konnect Mesh resources using HashiCorp Terraform.

Announcing Kubernetes Ingress Controller 3.5

We're happy to announce the 3.5 release of Kong Ingress Controller (KIC). This release includes the graduation of combined services to General Availability, support for connection draining, as well as the start of deprecating support for some Ingress types as we help move customers to the Kubernetes Gateway API. Let’s get into more details about these!

Ad Hoc Testing: A Quick Guide To Finding Hidden Bugs

Most software testing tends to follow a defined plan, with test cases listed in written form. However, sometimes the quickest way to find bugs is to use the application without any scripts in front of you, basically like a real user would do. This is the essence of Ad Hoc Testing. Ad Hoc Testing is an informal and mostly unstructured testing technique where you are relying purely on your brain and instincts instead of documentation.

Seamless Collaboration: Uniting Business and IT through Low-Code and Pro-Code Parity

Historically, software development clearly separated business and IT roles. Business teams defined the business requirements, while IT teams built digital experiences (e.g., customer-facing applications) based on these requirements. There was a continuous feedback loop where business teams reviewed and provided feedback, and IT teams made necessary changes until the digital experience was public-ready.