Please enable JavaScript.
Coggle requires JavaScript to display documents.
Separate Agent vs Partner portal - Coggle Diagram
Separate Agent vs Partner portal
To separate
CICD
Test job is separated, don't have to maintain both in same time
[pros]
Separate builds
[cons]
Not resource saving
[cons]
Test repo does not need to include out-of scope test cases - smaller size
[pros]
Test
Not to have to check test result for other user types
[pros]
Don't have to modify existing testcases whenever add new user type support
[pros]
Code
Easy to maintain - clean code/clean software design
[pros]
Take time to clone at first day - but this is one time task
[cons]
No businesses interferer between user types
[pros]
Design
Independent
[pros]
possible to reuse for look and feels
Security
Separate client id client secret
[pros]
Separate database for maintaining user session
[pros]
To not separate
Test
[cons]
to have to add/maintain fail cases for user types interfere
[cons]
to have to update existing test cases for specific user type
Reuse: Almost none - can clone keywords and modify, yes but volume of test will not be reduced
Code
[cons]
to switch user_type in code
[cons]
UI: switch case to support different pages permission for each user types
[cons]
Have to check for impact on each others when we develop features for each user type
[cons]
Build new/switch error message processing because there is no error mapping for external system user
[pros]
possible to have some reuse function but not much < 30% (this is product view, from tech view, we mostly still have to modify something inside reused function)
[cons]
to have update context path, change name of portal for something more generic
Design
[pros]
Save effort for some basic layout, general color, styles..
[cons] not being able to have separate look and feels in future
CICD
[pros]
build one service
[pros]
Save resource
[cons]
When test for partner function but test job somehow fails at agent function -> cost more effort to cross check
[cons]
heavy test repo - slow down test step in pipeline
Security
[cons]
using the same client id for different app type
[cons]
control API session and credential in same database - maintaining different security models in same app