whitestar cloud - up and running
TRANSCRIPT
WhiteStar Cloud - Up and RunningKevin WellerPrincipal, ASAP iSystems & Consultant, WhiteStar Corporation
Basic Data Flow
Email Example
From: [email protected]
Subject: WhiteStar Grid Order
COUNTY: CO:Jefferson
LAYERS: plss
COORDSYS: EPSG:4267
FMT: shapefile
Email Subsystems Decomposition
Cloud Deployment
Web Subsystems Decomposition
Domain Specific Language
vs. General Purpose Language
Web Pages, Insurance Policies, Combat Sim, etc.
FME
Dynamic Schemas & Generic Writers
Dynamic Schemas
Generic Writers
Modularization
Components
Why?
Clarity
Scalability
Flexibility
How?
Multiple Workspaces
Custom Transformers
Notifications
Why? Decoupling
Why? Flexibility
Where?
Issues Encountered
Modularity Challenges
Linked Custom Transformer Testing
Version Control Merge Conflicts
Testing Linked Custom Transformers
Running linked custom transformers in Desktop
Workaround: Temporarily Inline
Inline while implementing or making significant changes, then [re-]export
Feature Request
Version Control
“Versioning” of source files in system
Version History/Rollback, Branching & Merging
Examples
Subversion, TFS, SourceSafe, etc.
git + github.com
Merge Conflict Resolution Issue
Merge conflict
Two people affect same file
Automatic & manual
FME Workspaces/Transformers
Opaque File Format
Non-functional changes/rearrangements
Possible Solutions
Workspace/Transformer File Format Enhancements
Non-functional (eg. graphical moves)
Summary
Working system
Scalable
Good DSL
Effective implementation
Thank You!
Questions?
App: cloud.whitestar.com
For more information:
Robert White, [email protected]
Kevin Weller, [email protected]
WhiteStar Corporation and ASAP iSystems
Twitter: @doxotter (Kevin) and @k0rcw (Robert)