Platform for interactive microservices
Qworum helps stream-aligned devops teams modularize the UI layer of microservices-based enterprise software systems. Applications can be built by combining interactive services that may be hosted anywhere on the web, both on the Internet and in company intranets. Microservices architectures enable rapid software delivery by allowing different parts of a software system to be developed, deployed and updated in parallel by different teams within an organization and also across organizations. Microservices architectures organise developer teams around vertical slices of software systems rather than the horizontal UI, business logic, and data layers. In order words, microservice teams are responsible for all of these 3 layers within the boundaries of a particular slice. For microservices architectures, having a monolithic component at the UI layer represents a bottleneck for the software development lifecycle, because the team responsible for the UI monolith cannot scale with the number of microservices. Today, the only solution that software developers have at their disposal for breaking UI monoliths into smaller parts involves micro frontends. Micro frontends are UI components that are plugged into dashboard-style web pages for building web applications. In this case web applications become simple containers for micro frontends. Micro frontends are implemented using various technologies such as React.js components, web components or iframes, none of which are specific to microservices architectures. Besides being only suitable for dashboard-style applications, other limiting factors for micro frontends include: Qworum is a UI technology that was made specifically for microservices architectures. In contrast to micro frontends, which are parts of web pages, Qworum takes the web-API approach to user interaction. In effect, Qworum defines a new type of web API where each end-point can receive data, interact with the end-user if needed, and then return a result. Note that Qworum services are not components embedded in web pages. Rather, they offer full-page UIs to end-users. Also, in contrast to micro-frontend solutions where there are two types of entities (micro frontends and container applications), with Qworum everything is a Qworum service, including applications. So, while Qworum complements micro frontends rather than making them obsolete, by the same token Qworum does not have many of the limitations that micro frontends are burdened with:Solving the performance bottleneck that monolithic frontends represent
What are microservices architectures?
What is wrong with monolithic user interfaces?
Are micro frontends the right solution?
Interactive microservices with Qworum