Skip to content

chore(blog): add singapore summary #4056

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

Merged
merged 19 commits into from
May 26, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
158 changes: 158 additions & 0 deletions markdown/blog/2025-singapore-conf-summary.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,158 @@
---
title: "Bringing Asynchronous APIs to the Forefront at APIDays Singapore"
date: 2025-05-26T06:00:00+01:00
Copy link
Contributor

@coderabbitai coderabbitai bot May 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Update publication date as requested by content team
thulieblack requested changing the blog date to the 12th for consistency with the release schedule. Please update the date field accordingly.

Suggested diff:

- date: 2025-05-26T06:00:00+01:00
+ date: 2025-05-12T06:00:00+01:00
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
date: 2025-05-26T06:00:00+01:00
date: 2025-05-12T06:00:00+01:00
🤖 Prompt for AI Agents
In markdown/blog/2025-singapore-conf-summary.md at line 3, the date field is
currently set to 2025-05-26T06:00:00+01:00 but needs to be updated to the 12th
of May for consistency with the release schedule. Change the date value to
2025-05-12T06:00:00+01:00 to reflect the correct publication date as requested
by the content team.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thulieblack Can you please confirm that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes this is fine thanks

type: Communication
tags:
- Project Status
- Conference Update
cover: /img/posts/marketing-images/singapore-conf/singapore-header.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: "AsyncAPI kicked off its 2025 conference with a packed track at APIDays Singapore—the first ever AsyncAPI presence at an APIDays event in Asia."
---

## Hello, Asia-Pacific

In the early days of AsyncAPI, it all began with a question:
**“What if developers could build event-driven systems as seamlessly as they build RESTful APIs?”**

What started as a side project has become an industry standard, backed by a global community of engineers, architects, documentarians, and educators from every corner of the world.

Over the years, we’ve shown up: at conferences, in GitHub issues and Slack threads, building not just tools, but a community. And in April 2025, we showed up somewhere new: **Singapore.**

Thanks to our sponsor and host, [APIDays Singapore team](https://www.apidays.global/singapore/). We couldn’t have asked for a better stage to kick off our 2025 conference journey.

[APIDays](https://www.linkedin.com/company/apidays-conferences/) remains a driving force for API innovation worldwide, and we are honored to be part of this story.

<Figure
src="/img/posts/marketing-images/singapore-conf/community-marketing-specialist.webp"
caption="Booth Moment With Our Marketing Specialist."
className="text-center"
/>
Comment on lines +30 to +34
Copy link
Contributor

@coderabbitai coderabbitai bot Apr 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add alt attributes to figures for accessibility
Each <Figure> should include an alt prop describing the image for screen readers.

Example diff for the first figure:

 <Figure
-  src="/img/posts/marketing-images/singapore-conf/community-marketing-specialist.webp"
+  src="/img/posts/marketing-images/singapore-conf/community-marketing-specialist.webp"
+  alt="Booth moment with our Marketing Specialist"
   caption="Booth Moment With Our Marketing Specialist."
   className="text-center"
/>

Apply similar alt additions to all other <Figure> components.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Figure
src="/img/posts/marketing-images/singapore-conf/community-marketing-specialist.webp"
caption="Booth Moment With Our Marketing Specialist."
className="text-center"
/>
<Figure
src="/img/posts/marketing-images/singapore-conf/community-marketing-specialist.webp"
alt="Booth moment with our Marketing Specialist"
caption="Booth Moment With Our Marketing Specialist."
className="text-center"
/>

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alt was added as caption

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

# Look for the Figure component definition
fd Figure --extension jsx --extension tsx --extension js --extension ts

Length of output: 131


🏁 Script executed:

# Check the Figure component implementation
cat components/Figure.tsx

Length of output: 1653


🏁 Script executed:

# Check the type definition for Figure props
cat types/components/FigurePropsType.ts

Length of output: 98


@thulieblack You're right! Looking at your Figure component implementation, I can see it automatically uses the caption as the alt attribute for the image when no specific altOnly prop is provided:

// From your Figure.tsx component
const alt = altOnly || caption;
// ...
<img className={`${imageClass}`} src={src} alt={alt} data-testid='Figure-img' />

This means your images are technically accessible to screen readers. For most use cases, this approach works well when the caption adequately describes the image content.

Your component also supports an altOnly prop if you ever need to provide alt text that differs from the caption, which is useful when the visual context and screen reader description need to be different.

(_/)
(•ᴗ•)
/ >🧠


✏️ Learnings added
Learnt from: thulieblack
PR: asyncapi/website#4056
File: markdown/blog/2025-singapore-conf-summary.md:26-30
Timestamp: 2025-04-25T10:47:37.456Z
Learning: In the website's custom Figure component, the caption text is automatically used as alt text for images when no specific altOnly prop is provided. The component sets alt text using: const alt = altOnly || caption; This ensures basic image accessibility for screen readers.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.


## First Time in Southeast Asia

There’s something special about firsts: the first version of a spec, the first contributor, the first working group, the first time you explain what “event-driven” means to someone and see the lightbulb go off. This made us ecstatic to kick off the AsyncAPI Conference in Singapore.
On April 15–16, the AsyncAPI Conference was part of the [APIDays Singapore](https://www.apidays.global/singapore/) track. The event, themed "Where APIs Meet AI: Building Tomorrow's Intelligent Ecosystems", providing an excellent platform to introduce AsyncAPI to the vibrant Asia-Pacific community.​

<Figure
src="/img/posts/marketing-images/singapore-conf/asyncapi-x-community.webp"
caption="Ankit Interacting With The Audience at The Booth."
className="text-center"
/>

The AsyncAPI track had an overwhelming interest. Sessions were filled with attendees eager to explore the nuances of asynchronous APIs and event-driven architectures. The enthusiasm underscored the growing relevance of AsyncAPI in modern API development. And that mattered to us because it showed interest and proved that the problems we’re solving resonate globally.

## What We Shared And What We Learned

We opened our track with a talk titled “Multi-Protocol Async APIs: Designing a Unified Interface for EDA” by [Naresh Jain](https://www.linkedin.com/in/nareshjain/), Founder & CEO at [Specmatic](https://www.linkedin.com/company/specmatic/). Naresh opened the track by exploring the complexities of event-driven systems built on multiple protocols. He shared a design-first approach to unify these interfaces, allowing teams to tame the chaos and design with confidence early in the project.

<Figure
src="/img/posts/marketing-images/singapore-conf/naresh.webp"
caption="Naresh presenting Multi-Protocol Async APIs."
className="text-center"
/>

Next was [Tamimi Ahmad](https://www.linkedin.com/in/atamimi1/), Senior Developer Advocate at [Solace](https://www.linkedin.com/company/solacedotcom/) presenting "The Untapped Potentials of AsyncAPI Studio"

Tamimi showcased AsyncAPI Studio’s newest capabilities—making async design more accessible, visual, and powerful than ever. His live walkthrough had folks taking notes and asking how they could integrate the Studio into their team workflows.

<Figure
src="/img/posts/marketing-images/singapore-conf/tamimi.webp"
caption="Tamimi presenting the Untapped Potentials of AsyncAPI Studio."
className="text-center"
/>

[Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), Head of Technical Marketing at [Kong](https://www.linkedin.com/company/konghq/), spoke on "Enhancing Kafka Security and Control with Event Gateways."

Hugo brought his deep expertise in Kafka to the table, explaining how event gateways provide much-needed visibility, governance, and access control in Kafka-based environments. Security in EDA isn’t optional, and this talk proved why.

<Figure
src="/img/posts/marketing-images/singapore-conf/hugo.webp"
caption="Hugo presenting Enhancing Kafka Security and Control with Event Gateways."
className="text-center"
/>

We wrapped up the track with [Ankit Kumar](https://www.linkedin.com/in/ankit28/), Head of Developer & Customer Success at [Aklivity](https://www.linkedin.com/company/aklivity/), speaking on "Streamlining Event-Driven API Design."

Ankit gave us an exciting dive into AsyncAPI v3, our next major milestone. He shared what’s changing, why it matters, and how v3 brings clarity and flexibility to designing and managing complex event-driven APIs.

<Figure
src="/img/posts/marketing-images/singapore-conf/ankit.webp"
caption="Ankit presenting Streamlining Event-Driven API Design."
className="text-center"
/>

We had:

- Real-world examples of AsyncAPI in action
- Live demos using AsyncAPI Studio and the CLI
- The tooling and ecosystem that surrounds the spec

But more than the slides and demos, it was the questions that told the story:

- "Tell me more about AsyncAPI"
- “How do I introduce AsyncAPI into our hybrid systems?”
- “Can I use this with Kafka and MQTT?”
- “How do we contribute to the spec or tooling?”
- "How do other AsyncAPI adopters use AsyncAPI?"

We sensed not just curiosity, but a real readiness to act, this wasn’t just a learning moment; for many, it was a turning point.

<Figure
src="/img/posts/marketing-images/singapore-conf/singapore-conference.webp"
caption="AsyncAPI track in motion."
className="text-center"
/>

By the end of the conference, we had:

- Welcomed over 20 new faces to our Slack and GitHub communities, though we also noticed some hesitation to join the Slack community.
- Sparked contributor interest in tooling, docs, and protocol support

<Figure
src="/img/posts/marketing-images/singapore-conf/community-and-singapore.webp"
caption="Community Interaction at the Singapore Conference."
className="text-center"
/>

## What This Means for Us And What’s Next?

This event was a reminder: AsyncAPI is no longer just an open source project; it’s a global movement. Being in Singapore meant expanding our reach, connecting with new markets, and hearing firsthand how our tools and standards can solve real-world challenges.

It also sets the tone for the rest of 2025. With conferences scheduled for Munich, Lagos, London, Bangalore, online, and Paris, this marked our first step in a year of global community building. Conference designed to bring together developers, architects, technical writers, DevRel folks, and API enthusiasts who are passionate about the future of event-driven APIs.

We would love to have you attend any of these events close to you, but more than that, we would see you submit your proposal to speak. Whether you’re looking to share your story, demo your tools, or connect with the global async ecosystem, this is your chance. Our Call for Papers (CFP) is now open for most events, we’d love to hear from you!

- [Munich 🇩🇪: July 2–3, 2025](https://conference.asyncapi.com/venue/Munich)
- [Lagos 🇳🇬: July 18–19, 2025](https://conference.asyncapi.com/venue/Lagos)
- [London 🇬🇧: September 22–24, 2025](https://conference.asyncapi.com/venue/London)
- [Bangalore 🇮🇳: October 8-9, 2025](https://conference.asyncapi.com/venue/Bangalore)
- [Online 🌐: October 29, 2025](https://conference.asyncapi.com/venue/Online)
- [Paris 🇫🇷: December 9–11, 2025](https://conference.asyncapi.com/venue/Paris)

<Figure
src="/img/posts/marketing-images/singapore-conf/asyncapi-folks.webp"
caption="See You at Our Next Event."
className="text-center"
/>

If you joined us at APIDays, welcome to the community.
If you missed us, don’t worry, we’re just getting started.

Here’s how to stay in the loop:

- Join our [Slack](https://join.slack.com/t/asyncapi/shared_invite/zt-32hejdicx-NrD~boRq71gpCBJAM8mFoA)

- Explore the [Docs](https://www.asyncapi.com/docs)

- Try the [Studio](https://studio.asyncapi.com/)

- Contribute via [GitHub](https://github.com/asyncapi)

And if you're in Asia and thinking, "We’d love to run a workshop or AsyncAPI session in our community,” please reach out. We’d love to support you.

Until next time, see you Asia-Pacific!
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading