You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

ServiceComb Saga Frontend will be a web based application which shows all the necessary informations related to the transactions happening through Saga.

Currently the Saga Web module doesn't provides the list of transactions, providing the list of transactions and it's status to the users will be very helpful to the users/developers in development as well as in production env.

So here is the proposal to re-design the complete Saga Web and add all the necessary informations to the Web.

Technology Used

As the current Saga Web module is based on the combination of AngularJS and SpringBoot App for backend and this can be ideal solution for the new Saga Frontend so we can follow the same technology.

Api Used

We will be using the `/events` (GET) of Alpha Server to fetch the list of events from the DB. Based on the output of this API we can manipulate the Data and showcase the Dashboard as well as Transactions List.

Web Pages

Saga Web will mainly consist of 3 Pages as per the below hierarchy (This is a Concept, the actual implementation might have some variation based on the feedback from community)

  1. Dashboard (Landing Page)
    1. Recent Transaction Trends (Last 7 days - the time will be configurable from the UI itself)
    2. Recent Successful Transaction Trends (Last 7 days - the time will be configurable from the UI itself)
    3. Recent Failed Transaction Trends (Last 7 days - the time will be configurable from the UI itself)
    4. Total Saga Transactions Count
    5. Total TCC Transactions Count
    6. Total Successful Transactions
    7. Total Failed Transactions
    8. Preview of last 5 Successful transactions
    9. Preview of last 5 Failed transactions
  2. Transactions (2nd Page - Side Menu)
    1. List of All Successful Transactions (Filters will be available on all levels : microservice name, instance id, global ID, parent ID, event type, compensation method..etc..)
    2. List of All Failed Transactions (Filters will be available on all levels : microservice name, instance id, global ID, parent ID, event type, compensation method..etc..)
    3. Failure Rate (based on all microservices as well as based on particular microservices)
    4. Sub-transactions (Based on microservice)
  3. Transactions Tracing (3rd Page - Side Menu)
    1. Trace of Recent transactions and complete flow of Sub-transactions (similat to Zipkin tracing view) (filters will be available based on microservice name, transactions id's) 


Dashboard (Concept)


Transactions List (Concept)

  • No labels