Question

1
Replies
222
Views
SreekumarK8778 Member since 2014 10 posts
GM Onstar
Posted: 3 years ago
Last activity: 3 years 2 months ago
Closed

Best practices of packaging application and its dependencies

Best practices of packaging application and its dependencies

We have a number of applications that reuse common components. There are few options how these dependencies created:

  1. Package each component in its own Ruleset and include this Ruleset in the new application Ruleset stack

Example

“Application 1”

App1

App1Int

App1Data

AppCommonData

AppCommonInt

Service1Ruleset

Service2Ruleset

“Application 2”

App2

App2Int

App2Data

AppCommonData

AppCommonInt

Service1Ruleset

Service2Ruleset

  1. Package all common components in single application (of type framework) and “built on” the new application on this framework

Common FW app

AppCommonData

AppCommonInt

“Application 1” built on “Common FW app”

App1

App1Int

App1Data

Service1Ruleset

Service2Ruleset

“Application 2” built on “Common FW app”

App2

App2Int

App2Data

Service1Ruleset

Service2Ruleset

  1. Package each component in its own application and “built on” the new application on all common components applications

Item 3 example

Service1 App

Service1Ruleset

Service2 App

Service2Ruleset

Common FW app

AppCommonData

AppCommonInt

“Application 1” built “Service1 App”, “Service2 App”, “Common FW app”

App1

App1Int

App1Data

“Application 2” built “Service1 App”, “Service2 App”, “Common FW app”

App2

App2Int

App2Data

What is the best practice from prospective of code maintenance and deployment?

Low-Code App Development Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn