Application Architecting

This area of FLiP is primarily based on experience and personal style. Experienced architects know when to create one circuit instead of two, or two circuits instead of one. Architects also learn when and how to apply nested layouts most effectively. They can combine design patterns like MVC, other language resources like Java libraries in ColdFusion applications, as well as object-oriented requirements into a clean, extensible, maintanable and robust architecture.

Regardless of how you get there, you should end up with:
  • Circuits
  • Fuseactions
  • XFAs
  • Fuses (uncoded, AKA FuseStubs)
  • Fusedocs

Even with this structure, we still have not yet defined exactly how the code will work. We have simply defined the data interactions between the various pieces of the application. How will data be sent from one fuseaction to another? How will fuseactions be linked together? What data will come out of one fuse and be passed into another?

Since this is such a large topic, and oftentimes very specific to the individual application, check out the articles below.

When you're done architecting the application, now it's time to move onto the fun part: Fusecoding


Coming Soon
To help develop new Lasso Fusebox tools please contact us.

Copyright ©2019 LassoFusebox, All Rights Reserved.

Download from GitHub

Contact Us