With the dashboard development in action, now is a good time to look at CQRS design pattern. CQRS stands for “The Command and Query Responsibility Segregation” (CQRS) pattern. This design pattern separates read and update operations for a data store. In a traditional architecture, the same model is used to query and update database. That works for basic CRUD operations. In complex applications, we will end up creating more spaghetti code. A good use case is for dashboards where application has to restrict certain secure data based on user roles or add more complex joins based on a super users permissions. Implementing CQRS in these applications can maximize their performance, scalability, security and most importantly makes them flexible to better evolve over time.
Following is great article that went in depth about the CQRS design pattern:
CQRS: What? Why? How?
At BundleN, we experiment with stack combinations on our own time.
For potential clients interested in this stack, we can always give a demo of what we have up until that point of time. You can reach us at sales@BundleN.com
For more details on this stack, click here
Here is the latest about our Angular + Java project.
Backend API endpoint for new cases
Retrieve the case list with the following information as part of each case object
Retrieve the task list for the logged in user with the following information as part of each task object
Table View for New Cases
Provide a detail table with the new case information. As part of this table, add some icons to able to assign cases or flag cases.
Table View for My Cases
Provide a detail table view of the cases belonging to the logged in user. As part of this table, add some icons to able to edit cases or assign the case to someone else.
Table View for My Tasks
Provide a detail table view of the tasks pending for the logged in user.