About Designers

Designers in Intent Architect allow you describe your application's design as visual models and hierarchical concepts. For example, Designers could be used to describe: the entities in a domain, the services that make up the applications API, events that are published and subscribed, etc.

Designers are added to the Application when a Module that has designer configuration is installed. You can therefore choose which Designers you would like to use in your Application.

Domain Designer An example of a sample application showing a Domain Designer with a modelled domain.

Workflow Designer An example of a sample application showing a custom made Workflow designer modelling a bespoke workflow.

Designers serve as a blueprint of your system. They can be used to describe any aspect of your Application. The following are some examples of what they are used to capture:

  • Codebase Structure - Visual Studio Projects in .NET, Folder Structures in other languages, etc.
  • Entities - Entities and their relationships to one another, Domain Driven Design (DDD) concepts (Aggregate Roots, Entities and Value Objects), etc.
  • Database Schemas - Tables, Documents, Foreign keys, Indices, etc.
  • Services - RESTful web services, SOAP services, security settings, transactional settings, etc.
  • Client Proxies - Web client proxies, Synchronous Query Proxies, etc.
  • Eventing - Messages, Topics, Queues, Subscriptions, etc. Often used to support a Microservices architectures.
  • Workflows - Workflow Diagrams, Process Diagrams, etc.
  • Front-End Structure - Components, Routing, Modules, View Models, Views, etc.