We collect the latest Development, Anaytics, API & Testing news from around the globe and deliver it direct to your inbox. One email per week, no spam.
This guest blog was written by Matt Turner from Moesif. Moesif provides insights and tooling for API product owners to activate, understand, and monetize customers.
Ruby on Rails is an excellent choice for building a REST API, stemming from its design principles and robust feature set. It encourages a resource-oriented architecture, including built-in routing, migrations, and task tools. Rails also includes Active Record, an Object-Relational Mapping (ORM) layer, which simplifies database interactions.
The high-stakes world of software development is a race to deliver quality features, faster. When the testing phase of the development lifecycle is slowed by inefficient and error-prone processes, it’s impossible for teams to meet their deadlines. How can they keep up? By taking a smarter approach to test management that prioritizes efficiency without sacrificing quality. By implementing these four test management strategies, teams can work smarter and shorten their release cycles.
In this episode, hosts Sanjiva and Asanka are excited to have Christian Posta, a Service Mesh expert and Global Field CTO at Solo.io, join them. Together, they will explore the question: Is full lifecycle API management dead? They will discuss Christian’s article and the evolving landscape of API management. The conversation will also cover the Platformless manifesto and the important role of Internal Developer Platforms in modern software development. Lastly, Christian will share his thoughts on service mesh.
API adoption is at an all-time high. According to research by Coleman Parkes Research, 88 percent of enterprises use them. With API ecosystems, businesses can share their existing assets and capabilities with external parties. They can extend the value of these Application Programming Interfaces both internally and externally to share knowledge, tools and resources. Building an API ecosystem allow organizations to remain agile while delivering products faster than ever before.
Application programming interface keys are an essential part of using APIs. But what are API keys, exactly? API keys are authentication tokens in the form of unique strings of characters that allow you to access the data or web services an API offers. They act as a form of user authorization, proving that you are authorized to make requests to the API. In this article, we will discuss how API keys work and how you can use them to access the data offered by APIs.
In this video, Asanka Abeyweera demonstrates how to develop a basic integration using WSO2 Micro Integrator (WSO2 MI) as the integration technology and Choreo as the internal developer platform. Utilizing the AI assistance available in the new WSO2 MI VS Code extension, Asanka Abeyweera, Software Architect at WSO2 walks through the process of building, deploying, and testing the integration, along with showcasing basic observability features.
Data fabric technology can help in a significant way, which is why it’s becoming a go-to method of choice for data management. Data fabric technology integrates information scattered across disparate sources and creates a unified data model through a virtual data layer. Data fabrics let you leave your existing data architecture intact, pulling directly from your current data sources and updating them in real time. So why is a data fabric approach the solution to your complex data challenges?
Agencies typically have older procurement systems or too many systems. In either case, they are data entry intensive and error-prone, negatively impacting the procurement process and outcomes. The Office of Federal Procurement Policy’s Procurement Acquisition Lead Time memo from 2021 specifically calls for government modernization by “leveraging technology to modernize operations and help the workforce move from low- to high-value activities.”