You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
Verticles should communicate with each other by the
EventBus
.The text was updated successfully, but these errors were encountered: