Moving to the Cloud. Sam Hornstein Jetline Jason Nokes President, Distributor Central Garrett Ausfeldt Starline

Transcription

1 Moving to the Cloud Sam Hornstein Jetline Jason Nokes President, Distributor Central Garrett Ausfeldt Starline

2 Sam Hornstein

3 Current Services in the Cloud Business Management System (ERP) Website File Management Telephony Jetline has successfully migrated the above services to the cloud since Onsite hardware is primarily used for Network Security, Surveillance Systems, and custom application operations.

4 Provider Selection Criteria Providers NetSuite ERP / Web Box File Management Microsoft365 Fonality Telephony / VoIP Key Decision Making Factors Experience Stability Support Architecture Security / Infrastructure Cost Proven Track Record Gut feelings

5 Open mindedness Research Planning Testing More Testing Subject Matter Expertise Training Implementation Jetline staff was primarily responsible for all of the configuration, training, and implementation of all of our systems. It s critical to have an internal owner / champion behind the process. External resources were kept to a minimum and were leveraged in specific areas where expertise was required and we did not possess that skill / knowledge in house.

6 Jason Nokes President

7 Why Amazon Web Services Best performance after running comparison tests between AWS, Rackspace, and Azure Easy integration with other AWS products Only cloud provider to solve our DNS needs Have used S3 for years Future proofing: AWS continually releasing cool new products and price decreases.

8 Getting started and implementation Setup small test environments on each platform After we picked AWS we purchased support Took two people three months to complete Moved entire DC ecosystem to AWS EC2, S3, and Route53 Migration process was easier since we were already virtualized

9 Implementation and Beyond With replication there was minimal downtime AWS was reduction in load balancer features Backups more difficult had to be scripted but super fast (restore 6TB in seconds) 300% increase in performance 40% decrease in monthly hosting expense Still learning after 5 months in production

10 Garrett Ausfeldt

11 Amazon vs Azure Pros IaaS (Infrastructure as a service) market share leader Large technology partner ecosystem Suitable for any virtualized workload or environment Multiple data centers in close proximity Leader when it comes to pricing Cons Complexity of understanding and auditing bills Requires deep understanding to Architect

12 Azure Pros and Cons Pros Second in market IaaS share Modern easy to use user interface that will appeal to Windows administrators and developers Has PaaS (Platform as a service) capability. Users don t have to maintain the VMs themselves. You only maintain you application code Large Technology partner ecosystem Seamlessly extends and interoperates with on premise Microsoft infrastructure Cons Offering is currently very Microsoftcentric and offers little in the way of enterprise Linux options Still building up its partner network Multiple services are still in preview

13 Why Azure Learning curve not as steep as AWS A lot of great documentation and tutorials A familiar easy to use interface We are mostly a Microsoft shop Seamlessly integrates with our development environment Interoperates well with our current Microsoft infrastructure PaaS capabilities No need to worry about security, services pack updates, complicated configurations, etc. Saves resources and allows us to focus more on software development and innovation

14 Scalability Scale Vertically Add resources to a single node in a system. Scale Horizontally Add more node to a system. Horizontal scaling is a common within cloud environments Vertical scaling is less common due to the downtime required while the replacement is taking place.

15 Creating Cloud Ready Applications Don t code your application directly to a specific topology Build your application to be as generic and stateless as possible Don t assume local storage is permanent Put information in a remote store (e.g., SQL, NoSQL database) Design applications as a collections of services Build services and then combine those services into composite services or into applications. Scale the number of service instance s based on if the service load increases Design for performance Applications and services that run efficiently on your LAN, might not run efficiently on the open internet or distributed over a network

16 Panel Discussion Sam Hornstein Jetline Jason Nokes President, Distributor Central Garrett Ausfeldt Starline