-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore(blog): add-gravitee-sponsorship-2025 #4257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
iambami
wants to merge
17
commits into
asyncapi:master
Choose a base branch
from
iambami:gravitee-blog
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+63
−0
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
79c7693
chore(blog):add-gravitee-sponsorship-2025
iambami 68aa7b0
Merge branch 'master' into gravitee-blog
iambami 72ff279
fix(blog):add-gravitee-sponsorship-2025
iambami e3fe3fb
fix(blog):add-gravitee-sponsorship-2025
iambami 7f37f42
Merge branch 'master' into gravitee-blog
sambhavgupta0705 afd5029
Merge branch 'master' into gravitee-blog
TRohit20 b58ed1b
Merge branch 'master' into gravitee-blog
iambami f1dddec
fix(blog):add-gravitee-sponsorship-2025-new-changes
iambami 3debc77
Merge branch 'gravitee-blog' of https://github.com/iambami/website in…
iambami d95047d
Merge branch 'master' into gravitee-blog
iambami 27aabf9
Merge branch 'master' into gravitee-blog
sambhavgupta0705 a4c4b14
Merge branch 'master' into gravitee-blog
TRohit20 66dd4ab
Merge branch 'master' into gravitee-blog
sambhavgupta0705 0539b11
Merge branch 'master' into gravitee-blog
iambami 39a99e4
Merge branch 'master' into gravitee-blog
thulieblack 89117d5
Merge branch 'master' into gravitee-blog
TRohit20 40a2326
Merge branch 'master' into gravitee-blog
thulieblack File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| --- | ||
| title: "Gravitee Returns as a Platinum Sponsor: Strengthening the AsyncAPI Ecosystem Across 2025" | ||
| date: 2025-07-28T06:00:00+01:00 | ||
| type: Communication | ||
| tags: | ||
| - Project Status | ||
| - Marketing | ||
| cover: /img/posts/marketing-images/gravitee-community.webp | ||
| authors: | ||
| - name: Atinuke Oluwabamikemi Kayode | ||
| photo: /img/avatars/bami.webp | ||
| link: https://www.linkedin.com/in/atinuke-oluwabamikemi-kayode-5b838b1b7/ | ||
| byline: AsyncAPI Community Marketing Specialist | ||
| excerpt: 'Gravitee returns as a Platinum Sponsor, strengthening the AsyncAPI community and conference across 2025.' | ||
| --- | ||
|
|
||
|
|
||
| We’re happy to have Gravitee return as a platinum sponsor for both the AsyncAPI community and the AsyncAPI Conferences in 2025! Their renewed partnership is not only a show of continued support but also a reflection of their belief in the power of open standards, community-driven innovation, and modern API ecosystems. | ||
| Gravitee has long been part of AsyncAPI’s journey, not just as a sponsor but as an adopter, contributor, and champion of event-driven architectures (EDAs) that are secure, discoverable, and truly developer-first. | ||
|
|
||
| ## A Shared Vision: Open Collaboration, Stronger Infrastructure | ||
|
|
||
| AsyncAPI’s mission is to make working with event-driven systems as seamless as it is working with REST. That mission only becomes a reality when organizations across industries join forces to push it forward sharing knowledge, building tooling, contributing to the spec, and supporting our diverse global community. | ||
| Gravitee’s sponsorship is rooted in this shared vision. They understand that success in the API economy depends not only on robust tooling but on shared specifications and interoperable ecosystems. That’s why Gravitee has made AsyncAPI an essential part of its architecture, empowering teams to define, document, and govern their asynchronous APIs just as easily as their REST endpoints. | ||
|
|
||
| ## More Than Sponsorship: Investing in Community-Driven Growth | ||
|
|
||
| Gravitee’s renewed platinum sponsorship isn’t just a logo on a banner, it’s a commitment to sustainable, community-first growth. In 2024, their support helped us organize inclusive, impactful gatherings like AsyncAPI Conf Online and the Conference on Tour series now branded as the AsyncAPI Conference. | ||
| In 2025, their contribution helps us go even bigger, with in-person conferences in Lagos, Munich, Bangalore, London, Paris, and Online each designed to bring the AsyncAPI community closer together across regions and time zones. Gravitee’s support enables: | ||
|
|
||
| - Operational and travel cost for events. | ||
| - Broader outreach and visibility in growing the AsyncAPI communities around the world. | ||
| - Resources for speakers and panelists from diverse backgrounds. | ||
|
|
||
| When we say Gravitee is helping us “hold nothing back,” we mean it, they’re helping build an ecosystem where everyone can contribute, learn, and grow, no matter their location or technical background. | ||
|
|
||
| ## Gravitee + AsyncAPI: A Real-World Use Case | ||
|
|
||
| Behind Gravitee’s sponsorship is a real, practical investment in using the AsyncAPI specification to build and manage asynchronous APIs. Gravitee enables organizations to work seamlessly across protocols like [Kafka](https://kafka.apache.org/), [MQTT](https://mqtt.org/), and [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) using the AsyncAPI spec as a foundation for documentation, governance, and developer experience. This approach strengthens discoverability and observability across distributed systems, making Gravitee a natural ally in advancing AsyncAPI’s mission and ecosystem. | ||
|
|
||
| By adopting AsyncAPI, Gravitee: | ||
|
|
||
| - Enables better **discoverability** of event-driven APIs | ||
| - Enforces consistent **governance** across async interfaces | ||
| - Improves **observability** for systems using asynchronous messaging | ||
| - Reduces the **complexity** of managing hybrid architectures (REST + async) | ||
| This real-world usage supports AsyncAPI’s vision of making event-driven APIs easier to design, consume, and scale. | ||
|
|
||
| ## The Road Ahead: AsyncAPI x Gravitee in 2025 | ||
|
|
||
| As AsyncAPI continues to grow, expanding its tooling, maintainership, and governance, Gravitee’s support will help us scale with intention and care. From better docs and contributor onboarding, to new design systems and international webinars, Gravitee’s sponsorship helps bring these initiatives to life. | ||
| We're especially thrilled to have them with us at the **AsyncAPI Conference 2025**, as we bring together contributors, users, and curious minds from across the globe. Gravitee's support ensures that we can keep these conferences accessible and meaningful for all. | ||
|
|
||
| Thank you Gravitee for standing with us, and continuing to believe in the power of open, asynchronous systems. 💜 | ||
|
|
||
| ## Stay Connected | ||
|
|
||
| If you’d like to learn more about Gravitee, check out their [website](https://www.gravitee.io) and their social media links below: | ||
| - [LinkedIn](https://www.linkedin.com/company/gravitee-io/posts/?feedView=all) | ||
| - [YouTube](https://www.youtube.com/c/Graviteesource) | ||
| - [Facebook](https://www.facebook.com/GraviteeSource) | ||
|
|
||
| Stay tuned for more updates as we get closer to AsyncAPI Conference 2025! | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's repetition with line 28. Make section/line 28 focus on sponsorship, and then section/line 38 focus on use cases.