Ignite 2015 EU - Technology Breakout Session "Security, Stability and Scalability"
0 likes286 views
This document outlines the business model, security, stability, and scalability of a sales conference in 2015. The business model utilizes Scala, Clojure, JavaScript, Akka, JVM, and other technologies. Security features include multi-factor authentication, encryption of data at rest and in motion. Stability is achieved through a store first approach, queue-based processing, and decoupled connectivity. Scalability is ensured by automatic provisioning of environments, scaling based on utilization, distributing traffic, and alarms to trigger scaling activities.
Ignite 2015 EU - Technology Breakout Session "Security, Stability and Scalability"
- 1. Security, Stability and Scalability Sales Conference 2015
- 2. Business Model Security, Stability and Scalability Scala (Parallel Message Processing) Clojure (X-Form Logic) JS (Custom Functions) Akka 2.3 JVM 1.8 Ubuntu 12/04 Clojure 1.6 Rhino 5.4 Browser or Mobile HTML 5 Knockout JQuery Hazelcast CACHE Cloud Search QL Portal Auto Scaling Redundant Connectivity Array Integration Service Fabric Auto Scaling Availability Zone 2 Data Facade QL Portal Auto Scaling Redundant Connectivity Array Integration Service Fabric Auto Scaling Availability Zone 3 Data Facade Rabbit MQ AMPQ Quicklink 1.0 Integration Platform Smartlink 1.0 Applications Scala/Lift JVM 1.8 Jetty 9 Ubuntu 12/04 Authy Multifactor Authentication QL Portal Auto Scaling Redundant Connectivity Array Integration Service Fabric Auto Scaling Availability Zone 1 Data Facade S3 with AES 256 EU Region AWS Cloud
- 3. Security 4. Key based access to cloud infrastructure 1. QuickLink Portal: Multi Factor Authentication 2. QuickLink Connection: Two-Factor Authentication 3. Data Secured at Rest and in Motion
- 4. Stability 1. Store First Approach 2. Queue Based Processing 4. Decoupled Connectivity and Data Transformation 3. Multi-channel Data Handling
- 5. Scalability 1. Automatically provision environments 2. Increment or Decrement based on Utilization 4. Distribute traffic Across Instances 3. Alarms to Trigger Scaling Activities