there are a huge number of design patterns and components that are common to multiple projects and use cases. An example would be a contact list that describes users, etc, an inventory management subsystem, a logistic control subsystem. Given the orchestration nature of your framework, which is built on top of another orchestration framework,'Spring' you should be able to rapidly configure a complex system by importing existing subsystem designs directly onto the design canvas.
what about a catalogue of reusable designs that can be integrated into your application?
Hi @paulcahull7023, can you elaborate a bit more on what you mean? Are you referring to models you can use or to themes?
there are a huge number of design patterns and components that are common to multiple projects and use cases. An example would be a contact list that describes users, etc, an inventory management subsystem, a logistic control subsystem.
Given the orchestration nature of your framework, which is built on top of another orchestration framework,'Spring' you should be able to rapidly configure a complex system by importing existing subsystem designs directly onto the design canvas.