1 / 2

Elastic Analytic Computing – Business Case

Elastic Analytic Computing – Business Case. Pyxis Engineering is recognized within the IC for developing the HLT architecture Pyxis possess the technical capability and domain expertise required to make this product a success Verifiable market demand exists today

gizi
Download Presentation

Elastic Analytic Computing – Business Case

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Elastic Analytic Computing – Business Case • Pyxis Engineering is recognized within the IC for developing the HLT architecture • Pyxis possess the technical capability and domain expertise required to make this product a success • Verifiable market demand exists today • 2nd and 3rd parties that share analytics with HLT • Unable to afford millions of dollars in TIBCO software • Not limited to voice processing analytics • Can be extended to numerous variations of analytic processing • Can be marketed to other US government agencies • Estimating 2 FTEs for 12 months to develop operational capability • 1 Senior Architect (Brian Husted) • 1 Senior Software Developer (Kevin Faro) • 1 Senior User Interface Designer (needed for 2 months) • Working prototype within 6 months

  2. Elastic Analytic Computing – Technical Architecture JMS Server Service QUEUE Resource Manager Complex Event Processing User Interface Metrics Service Metrics Service Server Provisioning SLA Policy Starts Service Server Server • The Provisioning Controller – responsible for the on-demand placement/removal of services. • Java Message Service (JMS) – provides an asynchronous transport mechanism to invoke analytic services by placing a message in a queue. • Agent based monitoring – Hyperic captures and sends low-level metrics (CPU, memory, queue depths) that trigger dynamic provisioning decisions. • Spring containers – host the analytic services. • Graphical User Interface – provides monitoring visualizations, declarative command and control, and management of SLA policies.

More Related