2 min read

How Interface X works

Interface X architecture

Data journey: The frontend components collect user interactions or events. The wiring orchestrates the UI events by emitting actions for the client API through the adapter. The API returns the required data, travelling to the Vuex store through actions that can modify the app data state in the Vuex store with mutation objects. The UI components are bound to the data state, so that they render the new state to the user.

Understand how the pieces work together

The Interface X architecture is designed into separate tiers and elements:

  1. Presentation tier. Mainly represented by the UI components, responsible for determining how to display the data. It not only presents data in an understandable manner to users, but also monitors user interactions, emitting events to the Interface X application.

    Components can be customised according to client requirements, even allowing custom CSS styles.

  2. Orchestration tier. The x-factor in charge of orchestrating all the event wiring. When an event is emitted, other components are listening to it to react. This behavioural connection between components through events is the wiring. Then, the wiring decides what happens when an event is emitted in the Presentation layer.

    The wiring is customisable and flexible to meet client requirements. The behaviour can change without modifying the entire application. The event-driven operators in charge of the wiring routing logic enable different wiring configurations per event.

  3. Business logic tier. The heart of the app in charge of keeping all the data processing, where:

    • UI events emit actions for the client API. These actions can modify the state of the store.
    • The store holds all the app data that should be presented to the user at any given time. It acts as a single source of truth, providing great performance and reactivity.

The Interface X app needs an adapter to handle all client API communications. The API adapter mainly translates the related app data and use models to the client API and vice versa, solving any incompatibility issues. It is the entry point for all external data into the application.

The API adapter can be customised and extended to meet the client requirements. It’s a plug-in element that can be changed and adjusted to the specific client API, even when using other search services not based on the Empathy search API.

Architecture patterns

If you’re already experienced in the Vue universe, you’ll find the Interface X architecture somewhat familiar. Although the ViewModel layer (opens new window) of the MVVM pattern sprinkles traces all over the presentation tier, the Interface X architecture is basically inspired by the Flux pattern (opens new window) behind the state. As the X Components emit events that dispatch actions in the business logic tier, these actions can commit mutations to modify the state of the store. To sum up, the design of Interface X takes advantage of the MVVM and Flux patterns to design, develop, and configure each tier separately and independently.

Technical stack

coding tip

Interface X can potentially be integrated in commerce shops built with React. In any case, Interface X can be used in any webpage, as long as it is integrated as an isolated search layer.