Event & Tech PaaS platform
Background
Customer Request
Challenges & Solutions
Challenges
Lack of roles and access modes
The basic format of the module made it possible to create only typical system access without additional functionality or permission restrictions. It complicated the process of ordering catering and saving data in other system sections.
Weak system of user access protection
With the branching of modes and powers, it was required to strengthen data exchange protection and encrypted user information.
Lack of menu segmentation
To satisfy the rider of the teams serving the festival, the menus and culinary positions had to be optimized for the individual preferences of each team member at the festival, and their order through the module had to be automated.
Solutions
Creation of a hybrid system of module access
FTL specialists wrote their own algorithms to implement a hybrid access system, which allowed the provision of basic roles depending on user privileges and customize individual permissions for each user by the event organizer.
Implementing user authentication
After optimizing the roles, the development team implemented authentication technology to maximize connection and access security by logging the authorization process.
Catering order customization
FTL engineers created a custom menu for the festival, allowing selections based on meal periods, servings, and preferences (e.g., vegan, sugar-free). Orders were automatically sent to festival organizers for service company fulfillment.
project facts
main features
Implementing hybrid system RoR + React on the UI side of the platform
To optimize network speed, request processing, and fast rendering of module pages by dynamic components, FTL specialists performed server-side rendering for a React application using Ruby on Rails. It optimized the process of working with applications in terms of constantly changing infrastructure and reducing the operational load on the server in further scaling the platform.
Optimization of app and module development with Apollo GraphQL
In deploying new modules, the project management decided to abandon the use of Rest in the API completely. To improve the usability of the system, increase the flexibility of the data exchange process, and increase the efficiency of collaboration between front-end and back-end teams, the FTL developers transferred the platform to a GraphQL converter.
Technologies used
