Skip to content
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

Utilizing the core features of the Vert.x toolkit #1425

Open
dgarus opened this issue Mar 12, 2024 · 1 comment
Open

Utilizing the core features of the Vert.x toolkit #1425

dgarus opened this issue Mar 12, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request stale

Comments

@dgarus
Copy link
Contributor

dgarus commented Mar 12, 2024

It is common to specialize verticles by functional and technical concerns, such as having one verticle for exposing an HTTP API and another for dealing with a data store. This design also encourages the deployment of several instances of a given verticle for scalability purposes.
So we could implement the following verticles:

  • repositories HTTP API;
  • data storage;
  • administration HTTP API;
  • caching subsystem (slices, storage, repo configurations, users and so on);
  • access to a metadata database.

Verticles should communicate with each other by the EventBus.

@dgarus dgarus added the enhancement New feature or request label Mar 12, 2024
@dgarus dgarus self-assigned this Mar 12, 2024
Copy link

Issue is stale, CC: @artipie/maintainers

@github-actions github-actions bot added the stale label May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

1 participant