Building an API strategy, Redefining API discovery, AI in management, 5 rookie mistakes, APIs at Schneider Electric, writing an AsyncAPI file, & more.
Building an API strategy, Redefining API discovery, AI in management, 5 API rookie mistakes, APIs at Schneider Electric, Writing an AsyncAPI file, Microservices vs Monolith
Next week is our Consumer-Centric API Governance LiveCast! Tune in for our free hourlong webinar on governance tips featuring experts Kin Lane of Postman and Alianna Inzana of SmartBear. Wednesday, July 29, 9 AM PST. Register here.
The number of businesses that want to become API-fied has multiplied. However, these initiatives require a thought out strategy to succeed. In our featured article, Tanel Tähepõld shares holistic API strategy insights learned from his years building SaaS products.
85% of businesses consider web APIs and API-based integration fundamental to their business strategy and continued success. However, before starting with the digital strategy, we must have a well-defined business strategy and a set of goals. With an API-first development approach, we must have a valid business case before we build APIs to provide more value to your customers. A business strategy, customer success, and API strategy need to be aligned and work together to achieve the business goals...
API discovery is one such topic that, unfortunately, has evolved to become more ambiguous than before. API discovery has attracted more attention from the developer communities in recent times, partially because of the growth of APIs across various industries. With this growth of APIs, I mean both ways, i.e., building APIs to be consumed by others as well as consuming APIs built by others. Searching for APIs and testing them before using them in live products and services has become cumbersome due to the sheer large number of APIs that are available publicly.
Schneider Electric (SE) is a 184-year-old global company leading Digital Transformation in energy management and automation. We have been creating and managing APIs, using API management platforms since 2014. At the beginning of 2019, we felt the need to take stock of our API-estate and check it’s health. Subsequently, with the desire to fix issues, the top management took a firm decision to reset the API program to drive true transformation. To realize this API transformation, I defined and implemented the following nine steps...
Like APIs, Artificial Intelligence (AI) stands to streamline processes and make our lives and business that much easier. With the burgeoning reality of AI in API management, API systems will become increasingly fluid and intelligent, allowing consumers access to more specific and relevant information. AI has the potential to transform the API industry. By increasing security and improving efficiency at levels never before possible, this technology can reduce the human effort associated with API management while providing higher levels of precision. Here’s a look at how AI is changing the management stages of APIs, and a preview of the inevitable developments to come.
An API-first approach not only involves technical changes; it sometimes requires a significant cultural shift, especially for a big enterprise. Large companies are accustomed to working as per a certain model and structure, which might be completely opposite to the one required for an API-based approach. This makes it imperative for the stakeholders to spend a good amount of time churning out a proper strategy when deciding to implement an API program or set up an API ecosystem. From a business point of view, below are few things not to do when implementing an API strategy.
The AsyncAPI Specification is a comprehensive specification language for describing asynchronous messaging APIs. In this beginner’s guide to the AsyncAPI Specification, we’ll walk you through the process of creating your specification file, step-by-step. We’ll focus on the five objects every spec needs — the asyncapi version, info, servers, channels, and components — providing some mildly space-themed code snippets along the way.
In the world of programming, there are few terms as discussed (and misunderstood) as monoliths and microservices. Often positioned as a competing precedent and antecedent, the relationship between the two concepts is more complicated than meets the eye. Today, we’re going to define what monoliths and microservices are. We’ll also look at some advantages and disadvantages of both, as well as discuss the current trend of enterprise movement into microservices from the perspective of codebase complexity...
Nordic APIs is an international community of API practitioners and enthusiasts. Interested in contributing to our blog? Submit here. Want to speak at an event? Submit here.
