Overall Satisfaction with Lucidchart
We use it in engineering for software architecture diagrams of a microservices/serverless platform. We chart up microservice clusters, event flows, and deployment areas for wherein the cloud things are going to live, how the different areas connect, what has the source of truth is, etc. It also includes users, datastores, frontends.
- Data flow charting
- Service dependency charts
- Deployment diagrams
- Startup time could be quicker
- Sharing software architecture diagrams is simple.
- Embedding charts in confluence, slite, notion, etc to keep diagram and textual description close.
We embed the software architectural charts into the confluence documents describing those parts of the system, and into the descriptions of things to develop.
Do you think Lucid Visual Collaboration Suite delivers good value for the price?
Yes
Are you happy with Lucid Visual Collaboration Suite's feature set?
Yes
Did Lucid Visual Collaboration Suite live up to sales and marketing promises?
Yes
Did implementation of Lucid Visual Collaboration Suite go as expected?
Yes
Would you buy Lucid Visual Collaboration Suite again?
Yes
I've mainly used PlantUML for the same things. Doing it graphically with ease to move things around makes it much quicker than the technical coding of data flowcharts.