Community Requests

Model that a connection goes via something else to reduce noise on a diagram. Helps with event-driven architecture and any intermediary step This could tie in with the technology selection as well. Possibly show that intermediate object or add it to the diagram when you select it / show a flow dynamically so it's not there most of the time but shows the full story when you need it. This could allow you to add a connection directly from "Thing A" to "Thing B" and use the exact same connection from "Thing A" to the event bus to "Thing B." API gateways also have the same issue as queues. Firewalls also would be useful for this.

Instead of the current menu-driven nav (see screenshot), provide navigation via a collapsable tree structure. E.g. (but pardon the formatting!), Foo Level 1 -- Level 1 diagram 1 Level 2 -- Level 2 diagram 1 -- Level 2 diagram 2 -- Level 2 diagram 3 Level 3 -- Level 3 diagram 1 -- Level 3 diagram 2 Bar Level 1

Customer facing audit logging, export audit logs, stream audit lots to an external system.