[2017.02 Meetup #10] [TALK #1] Carlos Galveias - Serverless - Facts, Fictions, Challenges and lots of coffee

Microservices for dummies: do's and don'ts. An use case for Testing Services in devfactory.com: the motivation, challenges, consequences and results. Security and dangers in micro services. Private microservices using Fission, time permitting! :-)

Carlos Galveias: Programmer, Geek and Solutions Architect. He was the Software Architect responsible for microservices migration for Testing Services in devfactory.com.

Transcript

1. Serverless Facts, Fictions, Challenges and lots of coffee
2. Who am i? • My name is Carlos Galveias • Professional Geek • Software solutions Architect • Chief Architect and Manager of Testing Services at DevFactory • Founder of Siptel (a Portuguese VoIP provider) • Addicted to code
3. Serverless for dummies (does serverless means serverless?) • Serverless means “without servers” or does it? Not in this context. • So what are we talking about? Serverless is a reference to a computing ‘primitive’ as a function that is a deployable, invocable, scalable unit and a fundamentally different way to organize and architect applications. • There are servers Developers just don’t want to handle them.
4. What’s the fuss about serverless • For developers ◦ Focus on developing and not on handling server issues ◦ Faster development, deployment and test cycles ◦ No worries about underlying layer software updates, security, networking, etc • For Business ◦ No DevOps costs (YES, SAVE A LOT OF MONEY HERE) ◦ Scalability ◦ Pay per use (Scale to 0) ◦ Faster ROI
5. What’s the fuss about serverless #2 For Providers • They become the outsourced devops • Better management of underlying resources as they bill for units of computing, bandwidth, memory , etc. Instead of reserving capacity on servers that are idle all the time.
6. Do’s and Don’ts (Can everything be serverless?) • Stuff that you cannot (should not) make serverless ◦ Monolithic applications ◦ low latency and stream applications like rtp voice / video ◦ functions that require state ◦ Functions that require specific network protocols, endpoints and/or ports ◦ Things that require large amount of resources • Stuff that you should do serverless ◦ Everything that is stateless ◦ API’s ◦ Any event based task
7. Practical Use Case - Testing Services Testing Services is a software functional testing assembly line at DevFactory , a subsidiary from Trilogy that is a fortune 500 company Provides test development and execution on Trilogy/Versata group companies , testing software for Nasa, Lockheed Martin.
8. The Monolith (before)
9. The new Architecture (After)
10. Infrastructure Cost Comparison Yearly cost comparison *Estimated based on aws pricing OLD NEW Servers $10 000,00* $0,00 RDS $21 000,00* $3 000,00 DevOps Team $291 200,00 $0,00 All AWS $0,00 $11 994,00 Total Cost $322 200,00 $14 994,00
11. Service Statistics Number of tests running daily: 26.487 Lambda Invocations per minute: Max 4.532 , Average 2.000 Lambda Function Invocation time average: 10ms Storage: 1,43TB
12. Challenges • Develop everything from scratch • No pre-existing framework for develop and deploy functions • Logging • Throttling and Non documented limits • Slow database connections (Specially on Redshift) • Security • For devOps team, find another job
13. Security • Endpoint security - Use CORS effectively • Database - Not accessible to the public • Federated tokens - Temporary access tokens • Cryptography • Careful with IoT • DoS - Serious problem as you pay for invocations • Use keys and credentials as environment variables, not in the function code
14. Does serverless means DevOpLess? Immediately , no • Private serverless need.. servers and devOps • Many companies like banking, medical, insurance, etc cannot simply decide to go serverless as they have tons of legacy components, equipment, etc • Not everything is serverless In the future (fun discussion) • Trend is to automate Ops, so yeah, it will happen.
15. Private Serverless - An Opportunity • Restrictions and Strict data protection policies • Fear of putting sensitive data in public cloud • Developers will still want the benefits of serverless functional architectures Private Serverless frameworks • Fission - Abstract and orchestrate functions using docker and kubernetes. • OpenWhisk - IBM backed open source serverless framework
16. Thank You!
17. Links Me: www.carlosgalveias.com My Cloud Project: www.codethencloud.com Devfactory: www.devfactory.com Fission: http://fission.io/ OpenWhisk: https://developer.ibm.com/openwhisk/