Search the Community

The AsyncAPI specification emerged in response to the growing need for a standardized and comprehensive framework that addresses the challenges of designing and documenting asynchronous APIs. It is a collaborative effort of leading tech companies, open source communities, and individual contributors who actively participated in the creation and evolution of the AsyncAPI specification. Various approaches exist for implementing asynchronous interactions and APIs, each tailored to specific use cases and requirements. Despite this diversity, these approaches fundamentally share a common baseline of key concepts. Whether it’s messaging queues, event-driven architectures, or other asynchronous paradigms, the overarching principles remain consistent. Leveraging this shared foundation, AsyncAPI taps into a spectrum of techniques, providing developers with a unified understanding of essential concepts. This strategic approach not only fosters interoperability but also enhances flexibility across various asynchronous implementations, delivering significant benefits to developers. From planning to execution: Design and runtime phases of EDA The design time and runtime refer to distinct phases in the lifecycle of an event-driven system, each serving distinct purposes: Design time: This phase occurs during the design and development of the event-driven system, where architects and developers plan and structure the system engaging in activities around: Designing event flows Schema definition Topic or channel design Error handling and retry policies Security considerations Versioning strategies Metadata management Testing and validation Documentation Collaboration and communication Performance considerations Monitoring and observability The design phase yields assets, including a well-defined and configured messaging infrastructure. This encompasses components such as brokers, queues, topics/channels, schemas, and security settings, all tailored to meet specific requirements. The nature of these assets may vary based on the choice of the messaging system. Runtime: This phase occurs when the system is in operation, actively processing events based on the design-time configurations and settings, responding to triggers in real time. Dynamic event routing Concurrency management Scalability adjustments Load balancing Distributed tracing Alerting and notification Adaptive scaling Monitoring and troubleshooting Integration with external systems The output of this phase is the ongoing operation of the messaging platform, with messages being processed, routed, and delivered to subscribers based on the configured settings. Role of AsyncAPI AsyncAPI plays a pivotal role in the asynchronous API design and documentation. Its significance lies in standardization, providing a common and consistent framework for describing asynchronous APIs. AsyncAPI details crucial aspects such as message formats, channels, and protocols, enabling developers and stakeholders to understand and integrate with asynchronous systems effectively. It should also be noted that the AsyncAPI specification serves as more than documentation; it becomes a communication contract, ensuring clarity and consistency in the exchange of messages between different components or services. Furthermore, AsyncAPI facilitates code generation, expediting the development process by offering a starting point for implementing components that adhere to the specified communication patterns. In essence, AsyncAPI helps bridge the gap between design-time decisions and the practical implementation and operation of systems that rely on asynchronous communication. Bridging the gap Let’s explore a scenario involving the development and consumption of an asynchronous API, coupled with a set of essential requirements: Designing an asynchronous API in an event-driven architecture (EDA): Define the events, schema, and publish/subscribe permissions of an EDA service Expose the service as an asynchronous API Generating AsyncAPI specification: Use the AsyncAPI standard to generate a specification of the asynchronous API Utilizing GitHub for storage and version control: Check in the AsyncAPI specification into GitHub, leveraging it as both a storage system and a version control system Configuring GitHub workflow for document review: Set up a GitHub action designed to review pull requests (PRs) related to changes in the AsyncAPI document If changes are detected, initiate a validation process Upon a successful review and PR approval, proceed to merge the changes Synchronize the updated API design with the design time This workflow ensures that design-time and runtime components remain in sync consistently. The feasibility of this process is grounded in the use of the AsyncAPI for the API documentation. Additionally, the AsyncAPI tooling ecosystem supports validation and code generation that makes it possible to keep the design time and runtime in sync. Putting the scenario into action Let us consider Solace Event Portal as the tool for building an asynchronous API and Solace PubSub+ Broker as the messaging system. An event portal is a cloud-based event management tool that helps in designing EDAs. In the design phase, the portal facilitates the creation and definition of messaging structures, channels, and event-driven contracts. Leveraging the capabilities of Solace Event Portal, we model the asynchronous API and share the crucial details, such as message formats, topics, and communication patterns, as an AsyncAPI document. We can further enhance this process by providing REST APIs that allow for the dynamic updating of design-time assets, including events, schemas, and permissions. GitHub actions are employed to import AsyncAPI documents and trigger updates to the design-time assets. The synchronization between design-time and runtime components is made possible by adopting AsyncAPI as the standard for documenting asynchronous APIs. The AsyncAPI tooling ecosystem, encompassing validation and code generation, plays a pivotal role in ensuring the seamless integration of changes. This workflow guarantees that any modifications to the AsyncAPI document efficiently translate into synchronized adjustments in both design-time and runtime aspects. Conclusion Keeping the design time and runtime in sync is essential for a seamless and effective development lifecycle. When the design specifications closely align with the implemented runtime components, it promotes consistency, reliability, and predictability in the functioning of the system. The adoption of the AsyncAPI standard is instrumental in achieving a seamless integration between the design-time and runtime components of asynchronous APIs in EDAs. The use of AsyncAPI as the standard for documenting asynchronous APIs, along with its robust tooling ecosystem, ensures a cohesive development lifecycle. The effectiveness of this approach extends beyond specific tools, offering a versatile and scalable solution for building and maintaining asynchronous APIs in diverse architectural environments. Author Post contributed by Giri Venkatesan, Solace The post Bridging Design and Runtime Gaps: AsyncAPI in Event-Driven Architecture appeared first on Linux.com. View the full article

Image: “Open Source Springboard” by Jason Perlow, Bing Image Creator We all start studying and training in what we like with enthusiasm and optimism. However, as time goes by, difficulties arise, making us rethink our position and values. Are we good at what we thought we were? Are we heading in the right direction? Are we investing our time correctly? Do our skills define us? Who are we, after all? Shall we go on? Hopes and expectations always appear as two key concepts. They go hand in hand from the moment we think about what we want to train in, what we want to do, and how we imagine ourselves in the future. And if we are persistent, or we just made the right choices when choosing our studies, we finally go on: achieving goals, passing exams, and showing to ourselves and the rest of the people that we are improving our expertise and gaining knowledge. We can keep on with our path reaching what we thought was the top, at least at that point: we got a certificate! In the form of a BA, a Masters’s degree, or even a Ph.D. Reaching that point, we think we have completed something, but, on the contrary, doubts are more intense than ever. At least, the stats tell us we are not alone. Numerous studies show that it is common to suffer an existential crisis at the end of our studies. Be finally a grown-up, serious, predictable. It’s scary, sure. The abyss If there is one thing that the end of a training program leaves behind, it is emptiness. What do we know, after all? What can we do now? How can we apply what we have been trained for, after all? Responsibilities are coming closer. It’s impossible to run away. Make a career, make money, and be happy… and the feeling of approaching the abyss arrives in our minds. The fun is over. And begins the unavoidable. In most cases, the end of the training is perceived as the end of a critical period in our lives. However, it is more about what is coming next than what we left behind. The next stage began quickly. We need to get a job, be good people, and make a living. Be honest, humble, active, competitive, successful, friendly, fitter, happier, more productive… altogether… no stress. So, the questions reach an even higher level: Are we good at what we decided to devote our lives to? Are we attracted to what we are doing? Why should I do this? Are we doing something valuable? Are we making a real contribution? To whom? Are we free? Get off to a good start Fingers crossed, having a good start when choosing a first job is crucial in our careers. Ability or just luck. Whatever it takes. Getting into a good platform for landing in the professional realm can expand our horizons and increase our confidence in the long term. Fasten the seat belts! Not every company or project relies on newcomers with such confidence in their talent. But in the open-source context, AsyncAPI is safe territory for landing. As a growing project focusing on communication between asynchronous APIs, AsyncAPI is a suggestive place to start: evolving, open-minded, communicative, and empathetic… the project is all ears when talking about getting the best of talented people. Without hierarchy, no worries, and no pain, AsyncAPI shows itself as the best platform for coders starting to grow at their own pace. It fits like a glove. Since the beginning and throughout the different stages that the project has reached until today, the values and premises are clear, supported, and respected. Transparency and horizontality are unquestionable. People are at the forefront, and goals will come later. A welcoming atmosphere As an open-source specification, extensible and protocol-agnostic, AsyncAPI aims to make working with EDA as easy as doing it with RESTful APIs is today. Helping is the main contribution of the project: on the one hand, making messages more machine-readable and contributing to standardize communication; on the other hand, facilitating the work of developers working in that field. All that is in a work-based collaboration, co-creation, and engagement. They are undeniable. Nothing can be built without a bit of help from our new friends. That’s a whole new concept of what a work environment can be. Feeling comfortable, welcome, and trustworthy is the only way to create a sense of belonging. So, AsyncAPI mainly relies on accepting difference as a virtue and valuing trust in people to construct a solid and coherent community. This combination is probably the secret to the community’s constant growth and the project itself. Under these premises, AsyncAPI is increasingly involved in programs such as Google Summer of Code, Google Season of Docs, OpenForce, Outreachy, and even started AsyncAPI’s own Mentorship program. The main motto is that everybody has something to contribute. The more eyes, the more perspectives. The first and foremost skill is the willingness and eagerness to learn. All people are welcome, and someone is always ready to help those who need it. So, the idea of not knowing something can finally be empowering. Let’s watch it this way, as a blank page for starting—a fresh view. After an arduous journey, are we forced to forget our hopes and expectations when working? Can we still follow our dreams and make a living? Let’s not forget the ideals that pushed us at the beginning. Let’s not blur or erase the old memories of a young student daydreaming about the possibilities of a utopian Neverland. It’s worth being persistent and a lifelong learner if we know we are heading in the right direction together. Barbaño González The post AsyncAPI: A springboard for opensource professionals appeared first on Linux.com. View the full article

Image “Open Source Utopia” by Jason Perlow, Bing Image Creator “Technology is not neutral. We’re inside of what we make, and it’s inside of us. We’re living in a world of connections – and it matters which ones get made and unmade.” ¬Donna J. Haraway The body is the best and the only tool humans have for life; it is the physical representation of who we are, the container in which we move and represent ourselves. It reflects our identity, the matter that represents us socially. Humans have differentiated themselves from other animals by creating tools, using elements that increase their physical and mental capacities, extending their limits, and mediating how they see and understand the world. The body is, thus, transfixed and intermediated by technology. In the contemporary era, technological progress has led to global interconnection. Global access to the Internet has become the main propeller of globalization, a democratizing and liberating weapon. It is a place where the absence of corporeality manages to resituate us all at the same level. It is a pioneering experience in which the medium can favor equality. It offers a space of representation in which anonymity and the absence of gender and ethnic, and cultural constraints facilitate equal opportunities. A temporary autonomous zone The absence of a previous reference of a historical past turned the Internet into a “temporary autonomous zone.” Thus, a new space was constituted where identities could be expressed and constructed freer. In this way, the Internet has provided oppressed collectives and communities with a means of alleviating cultural and gender biases in which people express themselves free of socio-political pigeonholing. This same idea can be extrapolated to the new workspaces within technology. The modern workshop is on the network and is interconnected with colleagues who live in any corner of the world. This situation leads us to remote teamwork, multiculturalism, and all the positive aspects of this concept, creating diverse and heterogeneous teams where nationalities, ethnicities, and backgrounds are mixed. In this idyllic world of the liberation of identities and construction of new spaces to inhabit, the shadows of the physical world, with a dense and unequal past, creep in. Open source projects have faced all these opportunities and constraints in the last years, trying to achieve the goals expressed within the heroic times of the internet in the ’90s. Opening doors: For whom? For all? AsyncAPI is an open source initiative sustained and driven by its community. It is a free project whose objective is to be made up of everyone who wants to participate. It follows the basic idea of being created by everyone for everyone. Being part of the initiative is simple: join the Slack channel and contribute through GitHub. People join freely and form a team managing to take this project to a high level. But all freedom is conditioned by the context and the system surrounding it. At this point, AsyncAPI as a project shows its limitations and feels constrained. Talking about an open, inclusive, and enthusiastic community is a start. There is no widespread access and literacy to technology in all geographical and social contexts. Potentially and hypothetically, the doors are open, as are the doors to libraries. That does not mean that everyone will enter them. The clash against the glass ceiling makes up the technology field, specifically in software development. This conflict emerges from the difficulties of having a multicultural community rich in gender or ethnic identities and equality due to the limitations of the field. In 2019 the number of software developers worldwide grew to 23.9 million and was expected to reach 28.7 million software engineers by 2024. In these promising numbers, there are huge inequalities. The majority of developers come from specific world areas, and women represent only 10% of the total. Towards a utopian future: Let’s try it! The data shows us that beyond the democratizing possibilities of the Internet, most of the advances are only hypothetical and not real. We can see approximately the same numbers reflected in the AsyncAPI community. The community knows what is happening and wants to reverse this situation by being more heterogeneous and multicultural. That’s a challenge that many factors influence. AsyncAPI has grown in all directions, tackling this situation and creating an ecosystem that embraces variety. It comprises a community of almost 2,000 people of more than 20 nationalities from diverse cultures, ethnicities, and backgrounds. AsyncAPI was born as an open source initiative, a liberating software model in every sense, a code made by all and for all. It is not a model closed exclusively to the technological field but a movement with a solid ethical base that crosses screens and shapes principles. That is why AsyncAPI is committed to this model. No matter how many external factors are against it, there is a clear direction. The decisions taken now will be vital to building a better future – a freer and more inclusive one –. We do not want a unidirectional mirror where only some can see themselves reflected. The key is to search for a diverse and multifaceted mirror. Aspiring to form a community that is a melting pot of cultures and identities may seem somewhat utopian, but we believe it is a worthy goal to keep in mind and for which to strive. Proposals are welcome. Minds, eyes, and ears always remain open. Let us at least try it. Barbaño González The post Multiculturalism in technology and its limits: AsyncAPI and the long road to open source utopia appeared first on Linux.com. View the full article

Paper currency — which started gaining prominence in the 1600s — changed the face of global economics and ushered in a new era of international monetary regulation. The primary reason currency created such disruption was its ability to standardize the “medium of exchange”. APIs created a similar effect in the world of technology and digitalization by creating a standardized, reusable, and secure way to exchange information. Modern web APIs took shape in the early 2000s and played a key role in “.com”mercializing every business. APIs started as a connective tissue primarily relegated to a technical context and quickly evolved into a gateway to new business models, revenue streams, and ecosystems. In 2017, McKinsey estimated a total of $1 Trillion in profit could be up for grabs in the API economy. And in 2022, GGV Capital created an index of API-first startups — a generation of stylistically divergent SaaS companies with leaner operating cost structures and organic usage growth. Just as currency is going through an evolution from banknotes to digital wallets, the world of API management is also on the brink of change. With more than 15 years of experience managing APIs at Google-scale, we’ve got a unique vantage point from which to observe that change. In today’s post, we will spotlight seven API management use cases that we see growing in prominence — and how you can take advantage of these trends to future-proof your architecture. #1 “Shift left” in API security As a gateway to a wealth of information, APIs have also quickly become the primary attack vector in security incidents. When we surveyed 500 technology leaders, we learned that more than 50% of organizations experienced an API security incident in the last 12 months. Adding to the increasing magnitude of attacks, there are an increasing number of vectors for potential API security incidents like misconfigurations, outdated APIs/data/components, and bots/spam/abuse. These security issues aren’t just in production APIs, but at every stage in the API lifecycle. Notably, we found that 67% of the issues are discovered during testing as part of the release management process. This trend ushers in the need for forward-thinking organizations to “shift left with security” — moving controls earlier into the production workflow — by bringing security teams and API teams closer. To stay ahead of security threats, many organizations are actively looking for solutions that allow them to be proactive while minimizing the burden on their security teams. According to our research, integrating capabilities that proactively identify security threats (60%) is top of mind for most IT leaders for the next year. Source: 2022 API Security Research Report #2 “Knowledge graph” for your enterprise APIs It comes as no surprise that every organization is relying on APIs to expand and even ground their digital ecosystem — a network of partners, developers, and customers facilitated by modern, cloud-first technologies. There is a growing magnitude and variety of middleware assets, contributing to the growth of IT complexity. As the number of APIs continues to increase, there is a need to simplify consumption for internal and external developers. Even the most objectively useful APIs remain unseen by most of the organization. In turn this results in redundant code, reduced developer productivity, or worse — turned into a potential security attack vector. This complexity is shifting focus towards consolidation of all middleware assets, growing adoption, and improving education (see below) to improve developer efficiency and de-mystify the IT complexity. Source: 2022 State of APIs and applications This sprawl is a growing problem in the world of APIs, but it has a lot in common with an age-old phenomenon in the world of web pages and content—search. Google was born out of this problem to help organize the world's information. Similar to Google’s knowledge graph for web pages, there is a need to index, organize, and instantly present API information for developers that need it. Although it is an emerging practice, we see an increasing number of digital leaders and security teams in larger organizations with mature API programs invest in solutions that help consolidate all APIs, organize their information, and manage their lifecycle. #3 The imminent need for “omni” control planes APIs have taken on such a vital role in the modern application stack that they have slowly become the neural links across the entire enterprise architecture — bridging legacy and modern applications, shifting architectures towards microservices, and enabling operations across heterogeneous environments. To support all these technological decisions without sacrificing speed, organizations adopted multiple API gateways and fragmented API management solutions. However, this led to a lack of universal visibility, consistent governance, comprehensive security, and meaningful analytics across ALL the enterprise APIs (not just the ones within the confines of a given API management solution). And it increases the maintenance costs — fundamentally undercutting the value of APIs. With this evolution there is a growing need for an omni control plane — analogous to the brain in a human body — across all enterprise APIs. #4 API governance rising through the priority ranks Despite the clear need for governance, there is still no unified understanding on a good (or right) approach to API governance. With the rapid adoption of APIs without appropriate standardization or quality standards, API governance is top of mind for IT leaders, again. According to our research, 45% of IT leaders identified API governance as a critical component of their API program. The top three components of API security, performance analytics, and governance demonstrate the critical need for visibility, quality, and security across all APIs. Source: 2022 State of APIs and applications As digital consumers, we have seen this phenomenon across many industries and digital products. For example AirBnB disrupted the short-term rental market by providing standardized listings, detailed information, and high-resolution photos. In fact, the same governance phenomenon is ubiquitous in the world of e-commerce where there is a clear correlation between a high-quality website or product listing and increasing sales. The same analogy holds true in the world of APIs, as ~90% of developers use APIs in their work there is a direct correlation between the use of APIs and developer productivity. Digital officers and CIOs need to add appropriate governance controls to standardize API design and improve reuse without adding friction to development timelines. #5 Evolution of design patterns with multiple API gateways Adoption of new API architectural styles and microservices increased the complexity of the modern application stack. Our research found that 54% of organizations use a service mesh and API management in conjunction today to support the API gateway design pattern. In parallel, there is broad adoption of new protocols like GraphQL or AsyncAPI, outpacing the innovation in API gateways. For example, in a recent survey from DZone found that GraphQL accounted for 22.7% of application integrations. In response to this challenge IT teams are adopting multiple API gateways — by design — which is creating the need for complex communication patterns for future scalability. But the existing design patterns were mostly sufficient when client applications used homogeneous API protocols (Ex: REST). Although patterns like Backend For FrontEnd (BFF) intended to provide specific API interactions that are relevant on a per-client basis, they still did not account for complexities from multiple gateways and protocols. In response to the adoption of new protocols, there is a need to evolve the existing BFF pattern to account for multiple API gateways and protocols. #6 Driving green value chains with digital twins A digital twin is an effectively indistinguishable virtual representation of a physical object, system, or a process. For example the digital twin of a wind turbine (the object being studied) might be used to capture data like performance, rpm (revolutions per minute), or output captured by various sensors outfitted on the turbine. Digital twin adoption is growing and McKinsey estimates investments in digital twins will reach $58 billion by 2026 with a 58% CAGR. Every digital twin uses APIs to monitor, engage, and possibly control the physical asset. For example, Google created the Digital Buildings project — an open source, Apache-licensed effort to manage applications and analyses between a large heterogeneous portfolio of buildings. Sustainability is one of the driving forces behind the increased use of digital twins. As the need to reach net zero emissions accelerates, many organizations are tying performance (and in some cases even executive pay) to environmental, social, and governance goals. APIs help connect the dots between digital twins and sustainability. For example, an organization operating a manufacturing process could build a digital twin with APIs to collect behavioral data from sensors, monitoring systems, or other sources — which can eventually be integrated into the organization's digital platform or applications. These digital twins could be used to analyze and optimize the use of materials and energy, to minimize waste and emissions. Additionally, digital twins could be used to monitor and analyze the performance of systems over time, to identify opportunities for continuous improvement. Overall, APIs play a valuable role in supporting sustainability efforts by enabling digital twins, effectively driving more efficient operation of systems, and providing insights to improve environmental impact. For further examples, check out this video about driving a green value chain with APIs. #7 Commercializing access to data products The growing use of data-rich services (like IoT, ML models, remote access services, and web scraping, etc.) coupled with massive ingestion of data everyday is creating massive growth in data delivery paradigms like data lakehouses, data marketplaces, and data streaming systems (global data marketplaces alone are poised to reach $3.5 billion by 2028). Unfortunately, most of these systems are fragmented with almost no relationship or interoperability. APIs are filling this critical gap for organizations in two critical ways. First, APIs are providing standard and easy access to systems like data lakehouses or analytics hubs. Second, APIs are a key enabler of data products (digital products or services built using data as a core value proposition), a core component of any data sharing system. APIs provide a standardized way for different applications to interact with the data product. For example, an API could be used to allow a mobile app to access data from a weather forecast or a recommendation engine data product. Beyond data products, APIs also provide easy and standardized access various data management platform APIs continue to play a critical role in every application, experience, and ecosystem. Robust API strategies help organizations adapt to any architecture, business model, or environment in the face of changing technology landscape. Learn more about how Apigee is driving innovation and helping companies future proof their architectures to stay ahead of the top API trends.

We’re thrilled to announce that Gartner has recognized Google Cloud’s Apigee as a Leader in the 2022 Magic Quadrant for Full Life Cycle API Management, the seventh time in a row we’ve been recognized. We believe we are consistently recognized for the depth of our capabilities to help organizations monetize their data by creating external-facing API products and providing highly customizable developer portals. In this year’s report, Apigee has once again placed highest among the evaluated vendors for our ability to execute. At a time when organizations are in a bind with increasing pressure from disruptors and economic headwinds, IT teams are increasingly relying on APIs to do more with less. As the business value and critical volume of APIs increase, providing the right controls for development and operations teams is vital for our customers’ operational success - it’s a challenge we take very seriously and are honored by the recognition from our customers, users, and community. Year over year, API traffic and usage grows rapidly because APIs enable easier and more standardized delivery of services and data - and this in turn enables business growth. In fact research shows that organizations that adopt external APIs grow 38% faster than those that don’t. We believe that one of the reasons that the Gartner Magic Quadrant in API management is so competitive and highly valued is that building, managing, and securing APIs at scale is an immense challenge - finding the right vendor is a technology decision with a significant business impact. The Magic Quadrant helps you quickly ascertain how well technology providers are executing their stated visions and how well they are performing against Gartner market view. This report can be valuable in making the best API Management decision for your organization. Customers like Jackon National, Renault, Booking.com, L'Oreal, and Cathay Financial Holdings trust Apigee as their API Management partner. Our mission is to help our customers build an API strategy that drives organizational growth and digital excellence. We know that APIs are no longer just the connective tissue of applications, they’re now products that deliver unique customer experiences and revenue streams. While we believe we have been recognized for the investments we make day in and day out, we’re only getting started when it comes to Apigee product innovation. We’re continuing to invest in a few key areas: Commercial model flexibility - In August we launched Pay-as-you-go, a new consumption based pricing model that can enable you to unlock the value of Apigee with little upfront investment. While Apigee subscriptions continue to offer pricing predictability and can be cost effective at scale, Pay-as-you-go now lets you experiment with the flexibility to pay only for what you use, just like other Google Cloud products. We’re continuing to better align our commercial models to the needs of our customers. API Governance - We know from your feedback that easily discovering all the APIs in your organization and applying governance policies can generally be the best way to enable rapid , safe growth. That’s why this year we introduced a public preview of Apigee API hub, a universal API catalog that accommodates APIs of across styles (OpenAPI, gRPC/protobuf, AsyncAPI, SOAP/WSDL, GraphQL, etc) and lifecycle stages or gateway choices. We’re looking forward to enhancing this functionality at general availability. API Security - The rise in API traffic has unfortunately been accompanied by growth in malicious API attacks - API security is becoming the new battleground for business security. This year we released a feature of Apigee called Advanced API Security that helps make it easier to secure APIs by automating bot detection and identification of misconfigured APIs. We’re continuing to invest in API security with the urgency it demands, including leveraging Google Cloud’s AI/ML portfolio. Developer experience - Our users and their feedback are the very reason we’re here today - we’re never finished improving their experiences. For example, this year we launched the Apigee Cloud Code extension for VS Code, which enables API developers to build and test their Apigee API Proxies locally without connecting to a live Apigee Instance. These locally developed artifacts can then be staged for deployments as part of regular SDLC automation. We’re also continuing to invest in helping to make it easier to use Apigee with other products at Google Cloud - for example, customers can benefit from new integrations with Cloud Armor, and Anthos Service Mesh. Integration - The number of SaaS and custom built applications in use for business processes has continued to sky rocket. Now, organizations are faced with integrating these systems - which often requires time consuming custom coding and a full team of integration platform engineers. This is why we’re continuing to invest in Apigee Integration,which can improve productivity and agility by enabling you to create and configure new business process integrations - without code. In fact, we recently released a preview of Application Integration, the next generation of Apigee’s integration functionality, with core integration tools to help connect and manage the multitude of applications and data required to support business operations. We believe the Gartner Magic Quadrant is a good source of vendor evaluations, and we’re delighted that our ongoing investment in supporting our customers was recognized in this report. Most importantly, we’re thankful to our customers for the support and for sharing our belief that for Apigee, the best is yet to come. Download the full report here (requires an email address) or learn more about Apigee. Gartner does not endorse any vendor, product or service depicted in its research publications and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER and Magic Quadrant are registered trademarks and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and are used herein with permission. All rights reserved. This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Google. Related Article Introducing Pay-as-you-go pricing for Apigee API Management Access Apigee API management with no upfront commitment while maintaining flexibility to manage costs. Read Article

Docker Extensions build new functionality into Docker Desktop, extend its existing capabilities, and allow you to discover and integrate additional tools that you’re already using with Docker. More extensions are added every month, so let’s take a look at some of them released in September. And if you’d like to see everything available, check out our full Extensions Marketplace! InterSystems The new InterSystems extension is a convenient way to access InterSystems Container Registry right from Docker Desktop. It provides an integrated UI that contains public and private images for products like IRIS, IRIS for Health, and many more. With the extension, you can: Observe the list of public images available — and private images if you have access to WRC Filter images by name, tag, and ARM64 Easily pull images Delete local images Copy image name with tag Microcks Looking to Mock or test an API? If so, the Microcks extension can help. With Microcks, you can: Mock REST APIs importing local OpenAPI specification or Postman collections Mock GraphQL APIs importing GraphQL Schema and samples via Postman collections Mock gRPC APIs importing Protobuf and samples via Postman collections Simulate event-driven APIs (both on Kafka and WebSockets) importing AsyncAPI specification Test local REST, GraphQL, gRPC, WebSocket and Kafka endpoints to check conformance Bootstrap your API specification using Direct APIs Oracle SQLcl Client Tool Oracle SQLcl (SQL Developer Command Line) is a Java-based command line interface for Oracle Database. Using SQLcl, you can execute SQL and PL/SQL statements in interactive or batch mode. The Oracle SQLcl Client Tool extension provides: Inline editing Statement completion Command recall Support for your existing SQL*Plus scripts Volumes Backup & Share Volumes are the best choice when you need to back up, restore, or migrate data from one Docker host to another. With the Volumes Backup & Share extension, you can: Back up data that’s persisted in a volume (for example, database data from Postgres or MySQL) into a compressed file Upload your backup to Docker Hub and share it with anyone Create a new volume from an existing backup or restore the state of an existing volume Transfer your local volumes to a different Docker host (through SSH) Other basic volume operations like clone, empty, and delete a volume To learn more check out our blog post. Check out the latest Docker Extensions with Docker Desktop Docker is always looking for ways to improve the developer experience. We hope that these new extensions will make your life easier and that you’ll give them a try! Check out these resources for more info on extensions: Try September’s newest extensions by installing Docker Desktop for Mac, Windows, or Linux. Visit our Extensions Marketplace to see all of our extensions Build your own extension with our Extensions SDK View the full article

The Linux Foundation announced today that it now plays host to an AsyncAPI Initiative that has developed a specification and a suite of open source tools for asynchronous application programming interfaces (APIs) and event-driven architectures. Founding sponsors of the AsyncAPI Initiative include Ably Realtime, Apideck, Bump, IQVIA Technologies, Slack, Solace and TIBCO. Most recently, Postman, […] The post Linux Foundation Takes Control Of AsyncAPI Specification appeared first on DevOps.com. View the full article

The open specification for defining asynchronous APIs gains momentum, seeks neutral home for open governance, community growth and industry adoption SAN FRANCISCO, Calif., March 30, 2021 – The Linux Foundation, the nonprofit organization enabling mass innovation through open source, today announced it will host the AsyncAPI Initiative. AsyncAPI is a specification and a suite of open source tools that work with asynchronous APIs and event-driven architectures. It is the fastest-growing API specification according to a recent developer survey, tripling in production usage from 2019 to 2020. Founding sponsors of the AsyncAPI Initiative include Ably Realtime, Apideck, Bump, IQVIA Technologies, Slack, Solace, and TIBCO, and AsyncAPI recently announced a partnership with Postman. Today, AsyncAPI is in production at Adidas, PayPal, Salesforce, SAP, and Slack, among other enterprise environments. “As the growth of AsyncAPI skyrocketed, it became clear to us that we needed to find a neutral, trusted home for its ongoing development. The Linux Foundation is without question the leader in bringing together interested communities to advance technology and accelerate adoption in an open way,” said Fran Méndez, who created AsyncAPI in 2016. “This natural next step for the project really represents the maturity and strength of AsyncAPI. We expect the open governance model architected and standardized by the Linux Foundation will ensure the initiative continues to thrive.” AsyncAPI helps unify documentation automation and code generation, as well as managing, testing, and monitoring asynchronous APIs. It provides language for describing the interface of event-driven systems regardless of the underlying technology and supports the full development cycle of event-driven architecture. AsyncAPI is considered a sister project of the OpenAPI Initiative, which is focused on synchronous REST communication and is also hosted by the Linux Foundation. “The Linux Foundation is pleased to provide a forum where individuals and organizations can come together to advance AsyncAPI and nurture collaboration in a neutral forum that can support the kind of growth this community is experiencing,” said Chris Aniszczyk, CTO and Vice President, Developer Relations at the Linux Foundation. For more information, please visit: https://www.asyncapi.org Supporting Quotes Łukasz Górnicki, AsyncAPI “AsyncAPI at Linux Foundation is another brick needed to build a solid and sustainable community for the project. We are securing a perimeter for AsyncAPI and can focus on expanding the vision of making all the specs work together for the user’s good.” Bill Doerrfeld, NordicAPIs “Open standards are only as strong as their community effort. The details of the AsyncAPI charter represent their ongoing community mission and goal to retain vendor neutrality around the format. AsyncAPI is taking an active role in enacting this by limiting company representation per TSC, privileging work over money, and other strategies.” Kin Lane, Postman “AsyncAPI joining the Linux Foundation is the final cornerstone in the foundation of the open source event-driven API specification. This creates solid groundwork for defining the next generation of API infrastructure, beginning with HTTP request and response APIs, but also event-driven approaches spanning multiple protocols and patterns including Kafka, GraphQL, MQTT, AMQP, and much more. And all of that, in turn, will provide what is needed to power documentation, mocking, testing, and other critical stops along a modern enterprise API lifecycle.” Matt McLarty, Salesforce “Seeing how AsyncAPI has blossomed has been incredible. Its progress has been guided by two key principles in my opinion: a focus on solving real world problems, and a focus on community. As the world of synchronous APIs and event-based communication converges, AsyncAPI plays a vital role in levelling the API playing field.” About the Linux Foundation Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation’s projects are critical to the world’s infrastructure including Linux, Kubernetes, Node.js, and more. The Linux Foundation’s methodology focuses on leveraging best practices and addressing the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org. ### The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage. Linux is a registered trademark of Linus Torvalds. Media Contact Jennifer Cloer for Linux Foundation 503-867-2304 jennifer@storychangesculture.com The post Linux Foundation Will Host AsyncAPI to Support Growth and Collaboration for Industry’s Fastest-Growing API Spec appeared first on Linux Foundation. The post Linux Foundation Will Host AsyncAPI to Support Growth and Collaboration for Industry’s Fastest-Growing API Spec appeared first on Linux.com. View the full article

The open specification for defining asynchronous APIs gains momentum, seeks neutral home for open governance, community growth and industry adoption SAN FRANCISCO, Calif., March 30, 2021 – The Linux Foundation, the nonprofit organization enabling mass innovation through open source, today announced it will host the AsyncAPI Initiative. AsyncAPI is a specification and a suite of open source tools that work with asynchronous APIs and event-driven architectures. It is the fastest-growing API specification according to a recent developer survey, tripling in production usage from 2019 to 2020. Founding sponsors of the AsyncAPI Initiative include Ably Realtime, Apideck, Bump, IQVIA Technologies, Slack, Solace, and TIBCO, and AsyncAPI recently announced a partnership with Postman. Today, AsyncAPI is in production at Adidas, PayPal, Salesforce, SAP, and Slack, among other enterprise environments. “As the growth of AsyncAPI skyrocketed, it became clear to us that we needed to find a neutral, trusted home for its ongoing development. The Linux Foundation is without question the leader in bringing together interested communities to advance technology and accelerate adoption in an open way,” said Fran Méndez, who created AsyncAPI in 2016. “This natural next step for the project really represents the maturity and strength of AsyncAPI. We expect the open governance model architected and standardized by the Linux Foundation will ensure the initiative continues to thrive.” AsyncAPI helps unify documentation automation and code generation, as well as managing, testing, and monitoring asynchronous APIs. It provides language for describing the interface of event-driven systems regardless of the underlying technology and supports the full development cycle of event-driven architecture. AsyncAPI is considered a sister project of the OpenAPI Initiative, which is focused on synchronous REST communication and is also hosted by the Linux Foundation. “The Linux Foundation is pleased to provide a forum where individuals and organizations can come together to advance AsyncAPI and nurture collaboration in a neutral forum that can support the kind of growth this community is experiencing,” said Chris Aniszczyk, CTO and Vice President, Developer Relations at the Linux Foundation. For more information, please visit: https://www.asyncapi.org Supporting Quotes Łukasz Górnicki, AsyncAPI “AsyncAPI at Linux Foundation is another brick needed to build a solid and sustainable community for the project. We are securing a perimeter for AsyncAPI and can focus on expanding the vision of making all the specs work together for the user’s good.” Bill Doerrfeld, NordicAPIs “Open standards are only as strong as their community effort. The details of the AsyncAPI charter represent their ongoing community mission and goal to retain vendor neutrality around the format. AsyncAPI is taking an active role in enacting this by limiting company representation per TSC, privileging work over money, and other strategies.” Kin Lane, Postman “AsyncAPI joining the Linux Foundation is the final cornerstone in the foundation of the open source event-driven API specification. This creates solid groundwork for defining the next generation of API infrastructure, beginning with HTTP request and response APIs, but also event-driven approaches spanning multiple protocols and patterns including Kafka, GraphQL, MQTT, AMQP, and much more. And all of that, in turn, will provide what is needed to power documentation, mocking, testing, and other critical stops along a modern enterprise API lifecycle.” Matt McLarty, Salesforce “Seeing how AsyncAPI has blossomed has been incredible. Its progress has been guided by two key principles in my opinion: a focus on solving real world problems, and a focus on community. As the world of synchronous APIs and event-based communication converges, AsyncAPI plays a vital role in levelling the API playing field.” About the Linux Foundation Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation’s projects are critical to the world’s infrastructure including Linux, Kubernetes, Node.js, and more. The Linux Foundation’s methodology focuses on leveraging best practices and addressing the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org. ### The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage. Linux is a registered trademark of Linus Torvalds. Media Contact Jennifer Cloer for Linux Foundation 503-867-2304 jennifer@storychangesculture.com The post Linux Foundation Will Host AsyncAPI to Support Growth and Collaboration for Industry’s Fastest-Growing API Spec appeared first on Linux Foundation. View the full article