Why we are using Amazon Web Services?
Sep. 19, 2016•0 likes•333 views
Download to read offline
Report
Internet
Why we are using Amazon Web Services at Spark New Zealand as part of their innovation group; Spark Ventures
Pete YatesFollow
Recommended
Alexis Clarke_Recommendation LetterAlexis Clarke
Database Services at AWSAmazon Web Services
Lean Management - CEOs as ScientistsTami Reiss
360° monitoring of your servicesPanagiotis Moustafellos
2nd Athens DevOps meetupPanagiotis Moustafellos
OWF13 - October 3 - Raphael FerreiraParis Open Source Summit
More Related Content
Similar to Why we are using Amazon Web Services?
Spark NZ: Its kinda agilePete Yates
Astro’s Opening Guest Keynote at AWS Summit Kuala LumpurAmazon Web Services
AWS AWSome Day London July 2015 Ian Massingham
Opening KeynoteAmazon Web Services
Knowledge based economy and power of crowd sourcing knowdiff
Daniel Clayton (Treasury)AgileNZ Conference
Recently uploaded
informatica1.pptxAlessandroSichetti
roland barthes theory hw.pptxSerraSalci
Networking Basic Refresh.pdfCS Knowledge
AusNOG 2023: RPKI and whois updatesAPNIC
D2C Insider Elevate , Global Selling Summit Bengaluru - Worshop on Invitee re...D2C Insider
pdfjupitercpanel.pdfclay99
Why we are using Amazon Web Services?
- 1. Spark: Innovating in the Cloud A Spark Venture’s Story Pete Yates – Head Ops, IT & Platforms @peteyatesnz
- 2. Spark: Innovating in the Cloud 1st Sept 2 Our Ventures What is Spark Ventures? With over 300,000 customers
- 3. Spark: Innovating in the Cloud 1st Sept Why? 3@peteyatesnz
- 4. Spark: Innovating in the Cloud 1st Sept Supporting & growing 6 startups The Ventures could act like startups, we could not 4 Learn Fast & Act with Agility Mind-set Shift Keep $$ low People Scale $& Stability Guiding Principles “Build now, scale for later”
- 5. Spark: Innovating in the Cloud 1st Sept Why AWS? 5 Flexibility Business Alignment Velocity @peteyatesnz
- 6. Lightbox simultaneous streams Bigpipe subscribers 100% to 15-30 mins for env. builds 1day The last 12 months… Over 6m hours of content viewed 100% to 5-10mins for prod deployments 45mins
- 7. Spark: Innovating in the Cloud 1st Sept 7 Microservices Product Ecosystem Continuous Delivery Ecosystem Technology Ecosystem Infrastructure Ecosystem Open Source Contributions Spark Technology Capabilities Monitoring & Analytics CRM Mobile & Wearables Web App Test Automation Billing Payment Identity ISTM Technology Platform
Editor's Notes
- Show of hands: “Does any one know much about Spark Ventures?” Created 6 ventures from scratch - creation of lean Canvas to POC and business case and delivery Bigpipe – ISP Qrious – Big data platform Semble – mobile wallet Morepork – Home automation Lightbox – Video on Demand Public Wi-Fi Invest in 2 others Putti and Vigil
- Started Spark Ventures just over 3 years ago…why…to create new revenue streams available in the digital space as demonstrated by this recent study conducted by EY with global Telcos (TV and Video being at the top…so Lightbox fits the bill there). Traditional Telco revenues were declining or static at best…. “the reason Telecom is now Spark”
- Part of shared services group providing Ops, Customer Care, IT and Software Delivery to the Ventures Mindset shift – non traditional view of IT, automation, non silo’d way of working, multi skilled with cloud and SaaS experience, Keep costs low - they are start ups and as such want to keep their cost as low as possible People - Hiring a team based on attitude, fit, and their multi skills/experiences, customer first approach, happy to work in a fluid environment. Had to bring in experienced AWS resources (such as eIT) before we built up our skills internally. Collective recruitment, where team interviews potential candidate. Scale with Stability – Automate, grow as the Ventures grow, working with a hybrid environment Guiding principles - to base architectural decision on – such as cloud first, build now, scale for later, 80% fit is ok, automate and reuse, helped empower our people Optional Content High level over view of AWS: MultiAZ highly available dev/test/prod environment includes EC2 instances, Elastic Load balancer, RDS multi AZ instances, security groups, monitoring/logging (cloudwatch), SSL implementation.
- Flexibility Scale – can scale up easily as the business grows such as auto scaling or Reserved instances or shut down without affecting the other Ventures Cost – can attribute costs to a business (as we have created individual accounts per Venture), monthly fee, no need to buy expensive infrastructure especially as they were start ups. Hybrid model – work loads both in public and private clouds Business Alignment DevOps – Ops and Dev working closer together to deliver to sprint time frames (by attending Sprint Planning sessions), created a sandpit environment so that devs can start working on a POC while AWS team build proper environments. Closer relationships with Product Manager to ensure clear understanding of requirements and user stories Cloud first – supports our cloud first guiding principle DR – inherently in place due to using multi AZs Billing – understand costs, per month, look to optimise, we also use a 3rd party SaaS solution (Cloudyn) to assist us. Velocity Delivery – allows us to keep up with the rate of change required by the Ventures – standing up environments in a few hours for devs to start development work Automation – All builds are templated, we used Puppet but moved to Packer and Cloud Formation Deployments – can complete deployment to production in 5-10 mins Re-use as much as we can – designs to build templates
- A quick view of some Venture stats spinning up the environments from 1 day to 15-30 mins. Manual> Puppet> Packer Deployments – 5-10 mins using bamboo and Elastic bean stalk (EBS)
- A high level view of the under lying technology we use to create and support the Ventures