Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

Hosting of demo app - propose changes #161

Closed
derberg opened this issue Jul 24, 2023 · 7 comments
Closed

Hosting of demo app - propose changes #161

derberg opened this issue Jul 24, 2023 · 7 comments
Labels

Comments

@derberg
Copy link
Contributor

derberg commented Jul 24, 2023

Yo, do we need to host the demo app? Do we know if anyone is using it?\

I suggest we stop doing it as I wanted to propose we stop using Kubernetes in Digital Ocean:

  • we stop deploying event gateway to kubernetes and if someone wants:
    • there can be instruction about using docker compose
    • we can just deploy super minimal demo directly using DO droplets
  • we stop deploying server-api to K8s as well, and just use droplet to host it

It's all about money. K8s cluster costs $96 a month and we just ran out of all funds we had because of this high cost.

We did use K8s as we envisioned that we will have many different projects hosted there, so K8s was good option in case at some point of time we need to move somewhere else away from DO.

The future appeared to be different. Thus imho we should move away from K8s.

thoughts?

Of course I will ask DO to give us more budget. But this doesn't mean that we should continue what we do

@smoya
Copy link
Collaborator

smoya commented Jul 24, 2023

+1 to, at least, move this into a Digital Ocean app instead of K8s.
Regarding if it make sense to keep it alive... atm I would tell you nobody uses it or even used it in the past. So I'm up for letting it go.

Copy link
Contributor Author

derberg commented Jul 25, 2023

it surprises me that there are 51 stars, so looks like there is some interest.

So I'm up for letting it go.

letting it go, you mean the whole project, to archive?

@derberg
Copy link
Contributor Author

derberg commented Sep 28, 2023

letting it go, you mean the whole project, to archive?

right?

@smoya
Copy link
Collaborator

smoya commented Oct 2, 2023

it surprises me that there are 51 stars, so looks like there is some interest.

So I'm up for letting it go.

letting it go, you mean the whole project, to archive?

No, I meant shutting down the demo app :)
Regarding the interest, yes it looks like, but more about adding features or supporting other protocols rather than Kafka (like #158), but no interest in collaborating so far :(

It is sad this project is not active and in the AsyncAPI mid-term roadmap anymore. I still believe it could be very useful and powerful for people (we saw success on commercial solutions). But it requires a lot of effort (look at this low level test, for example...).

Copy link
Contributor Author

derberg commented Oct 2, 2023

from my point of view, if there is no interest and no time for active maintenance from your side, we should just notify the TSC that this project is a candidate to be archived, and is there anyone who is things it is a bad move and is willing to jump in and help

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@smoya
Copy link
Collaborator

smoya commented Feb 22, 2024

For the record, the demo app was shut down time ago.

@smoya smoya closed this as completed Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants