The document discusses the benefits and adoption challenges of serverless technology for startups, emphasizing the need for a mindset shift towards cloud-native solutions. It highlights various opportunities in cloud computing, the opportunity for rapid development and scalability that serverless offers, and the importance of community engagement in learning and sharing experiences. The speaker, Daniel Zivkovic, encourages startups to embrace serverless to overcome traditional development hurdles and succeed in a competitive landscape.

1. Startups + Serverless =
Match made in Heaven
www.ServerlessToronto.org October 30, 2018 Meetup
Daniel ZivKovic, Cloud solutions Architect
TriNimbus – an Onica Company

2. What to expect today?
• Presentation Style: 75% Cultural and 25% Technical
• Examples are from AWS, but principles are truly Cloud provider
agnostic
3. HOW TO
LEVERAGE
CLOUD?
2. WHICH ITCH
TO SCRATCH?
1. START WITH
WHY
4. SERVERLESS
ADOPTION
5. WHERE TO GO
NEXT?

3. 1. Start with Why

4. Why This Topic?
• Many of us in the Serverless Community were surprised about very
low Serverless adoption among Startups.
• Conducted a poll of successful Startup Founders (I know) to hear
their Point of View, and learned: Technology is about the LAST thing
Founders worry about!
Despite, how important
it is to start IT correctly
– and have a “smaller
rock to push”

5. Why Listen to ServerlessToronto.org?
• Home of “Less IT Mess”:
• Less Servers to Manage
• Less code to write
• Make work in the IT more purposeful & fun again
• We keep Learning…
• and sharing our experiences.
• How we run the User Group?
• Community comes first
• Corporate interest second
• Worldwide https://www.meetup.com/pro/serverless

6. Why Listen to Daniel?
• IT Veteran with 31-year of experience
• Seen it all, from when IT was 1-2 guys in the corner, till we “took over” office
spaces from the businesses… became dogmatic… and are now scrambling to
“plow through” the Digital Transformation.
• From “IT Mercenary” to “Serverless Missionary”
• Contractor since immigrating to Canada in 1992, till January 2018
• when I chose to join TriNimbus to do something meaningful with my life –
help simplify IT by spreading “serverless religion”.
• Failed a number of startups, so I can tell you what NOT to do
• Great Anti-Pattern for entrepreneurs 

7. 2. Which Itch to Scratch?

8. Opportunities for Building on Cloud
• Increment – faster, better, more scalable version of the same thing
• There is a clear market there
• Gap fillers – gaps close quickly so use it like a trampoline
• Product gaps that everyone can see, so you have to act quickly (e.g. when Docker came out
everyone wanted to do Enterprise version of Docker)
• Better to be really fast to market if you’re going to compete / gap-fill cloud provider
• Can be good to get you started, build momentum, but you cannot assume to own the gap
• Category creator – become Uber, Netflix, Docker “of thing”
• When no one understands what you’re doing, who would buy it, then start copying you
• They are the longshots – most of the attempts fail!
• Leverage – huge set of possibilities in the Cloud
• What can you for with GPU enabled monstrous machines, ML APIs (e.g. recognition)...

9. How do You Build The Leverage?
Wardley Maps show how
things evolve over time, and
move up the value chain:
• Everything starts new,
becomes a mainstream
products, then commodity
• Electricity => 20th century
reality
• Internet => e.g. Cloud
• Cloud => e.g. ML, Serverless
• ML/DL => e.g. Voice First
Technologies
• Serverless => ???

10. 3. How to Leverage Cloud?

11. Not All Cloud Options are Equal
Yes – everyone is choosing Cloud, but it’s such a broad term that there
is so many ways to do it incorrectly – out o the gate!

12. Everybody promises to give you solutions
following Cloud Native principles
• Self service – no waiting
• Pay as you go, afterwards – not what you will use next year
• Globally distributed by default – no need to build data centres worldwide
• High Available – distribute over Zones within a Region by default
• Elasticity – turn idle resources off (unlike most data centres)
• Immutable code – Automated builds, Ephemeral instances (pets vs. cattle),
Blue-green deployments, Versioned services
These principles remained the same, but
• technologies and practices keep evolving… nowadays towards Serverless.

13. Here’s a recent “Weather Forecast”
• Serverless is the future of AWS Cloud:

14. Why go Serverless-First, if you are Startup?
• Infinite scalability – when you become infinitely popular 
• Cost – don’t pay if nobody is using your systems
• Less Server Operations!
• Less lines of code to Maintain!
• Speed of innovation
• Serverless is New Agile – not by forcing people to “sprint faster”, but by using
standardized higher-level building blocks (like Lego bricks) to help developers iterate
and experiment faster.
• Serverless solutions may lack fine details, but are recognizable, easy to modify and
extend – just like Lego objects you build from “standard blocks”.
• And just like Lego does – you can optimize by building new custom components (to
look little bit more like the thing you wanted), which then becomes a new – more
specialized, common component in your toolbox.

15. Evolution of Business Logic (in plain English)
• A history of the Application Architectures condensed into 20 slides by
Adrian Cockcroft
www.slideshare.net/AmazonWebServices/arc219digital-
transformation/7
Slide #7

16. Evolution of Business Logic… continued
Slide #20: Microservices to Functions Slide #26: Microservices to Ephemeral Functions

17. 4. Serverless Adoption?

18. Visualize “The Lego Analogy”
Traditional Development Rapid Development Optimization

19. • Full custom design
• Months of work
• Custom components may be
fragile and need to be debugged
and integrated
• Too many detailed choices
• Long decision cycles
Traditional Development
• Building bricks assembly
• Hours of work
• Standard reliable components
scale and are well understood
and interoperable
• Need to adjust requirements to
fit the patterns available
• Constraints tend to reduce debate
and speed up decisions
Rapid Development
“Why Serverless First Is Like Building with Lego” – Adrian Cockcroft: https://youtu.be/5siD210Grr4

20. • Custom code and services
• Lots of choices of frameworks
and API mechanisms
• Where needed, optimize serverless
applications by also building services using
containers to solve for
• Lower startup latency
• Long running compute jobs
• Predictable high traffic
• Serverless events and functions
• Standardized choices
• Combine these building blocks
AWS Lambda
API Gateway
Amazon SNS, SQS
Amazon DynamoDB
AWS Step Functions
Containers Serverless
“Why Serverless First Is Like Building with Lego” – Adrian Cockcroft: https://youtu.be/5siD210Grr4

21. Technologies are NOT excluding one another
• Containers are THE serverless “engine” – just under the hood
• So people like me can focus on “driving” (taking business places), and
• remain ignorant about how “cars” (containers) work 
• We’re not saying Computing before Serverless is no good
• Our “religion” is all inclusive – “we believe” in everything before us 
• And there are Use Cases where Serverless is still not good technology
• As far as I’m concerned “Serverless = FaaS + BaaS”, so
• you just give me an API – however you choose to implement it, and
• SLA (service level agreement), and
you’ll be BaaS (Backend-as-a-Service) to me – because I don’t have to
manage it, nor worry about your uptime.

22. “Adopting Serverless for Greenfield is easy,
except for the people”
– Joe Emison:

23. “Not Invented Here” obstacle
• Some people are just stuck in the past
• Capitalizing on the past successes – and that’s OK.
• There is also worry abut Job Security
• Sometimes IT can feel like a Syndicate – protecting one another’s
jobs.
• The real problem is that
• IT industry is plagued by “Not Invented Here” syndrome
• Learn to love other people’s APIs like you love your own APIs! 
• With arrival of Scrum – not saying agile 
• IT became (too) often focused on making Developers “sprint
faster” – but going nowhere (driving business in circles).
• For success we need both good ideas & good implementations
(really experimentation), not just good looking Velocity Charts

24. 5. Where to go next?

25. Don’t follow the “White Rabbit” into Cloud
• Like Alice led into Wonderland by the
White Rabbit, geeks too easily fall into
“the rabbit hole”… and will take non-
technical people there too!
• We are lured into thinking we are
making progress, but
• the most subtle part of this “rabbit
hole” phenomenon is how unaware its
victims are.
• SOLUTION IS TO
• Keep learning, and
• exchanging experiences with others!
• Simplicity is the key.

26. Developer, Ops, QA, or DevOps Engineer?
• Join our www.ServerlessToronto.org Community
• Membership in our User Group – totally free, community driven, monthly meetups,
soon to have Slack channel, and the website… stay tuned.
• We are 100% CLOUD AGNOSTIC – so if you were “born in another Cloud”, please
reach out to me to arrange the “stage time”: Daniel.Zivkovic@gmail.com
• I did not chose to be born as Christian Orthodox, and my wife did not choose to be born as
Bosnian Muslim… but that DID NOT stop us from loving one another.
• So don’t let organizational choices divide us in the cloud too 
• The Community is always looking for mentors and knowledge sharing!
• Sign up for Serverless Workshops http://bit.ly/serverless-stack-workshop
• Run by www.Serverless-Stack.com creators Jay & Frank
• Low cost of entry

27. Business Owner?
• Challenge your IT Leaders to adopt Serverless mindset
• Ask me about AWS Landing Zone solutions: dzivkovic@onica.com
• A pre-configured, secure, multi-account AWS environment
• Automated • Scalable • Self-service
• Guardrails NOT Blockers • Auditable • Flexible

28. Four Quadrants of Competitive Landscape
Big
Slow
Big
Fast
Small
Slow
Small
Fast
Speed to Implement
Company
Size
Your Target

29. Enterprises Stuck in Digital Transformation
• Enterprises are bleeding in Dev vs. Ops vs.
DevOps wars, and cannibalizing one
another like the tribes of Easter Island:
• They have their hands tied behind
their back, so they are becoming
easier targets for faster competitors:

30. References
• Inspiration from Joe Emison – serial entrepreneur went through 4 “serverless
startups” in 3 years
• Serverlessconf San Francisco 2018: Better Application Architecture with Serverless
https://acloud.guru/series/serverlessconf-sf-2018/view/better-application-architecture-
with-serverless
• Serverless Patterns and Anti-patterns https://www.infoq.com/presentations/serverless-
patterns-antipatterns
• Wisdom (and number of slides) from Adrian Cockcroft – the man behind
Netflix's AWS Cloud strategy, and my “boss” in Sun Microsystems days
• AWS re:Invent 2017: Digital Transformation (ARC219)
https://www.youtube.com/watch?v=aLSFGLJ6Byo
• AWS Topics (sampler)
https://www.youtube.com/playlist?list=PL_KXMLr8jNTnwkzV7SePa0jHFUG2qn0MA
• Strategy from Simon Wardley – UK Researcher (funny too “Mel Brooks of IT”)
• KubeCon Keynote: Crossing the River by Feeling the Stones
https://www.youtube.com/watch?v=xlNYYy8pzB4
• Slides: https://www.slideshare.net/opensecsummit/wardley-maps-sec-15-keynote
• Experience is my own – and it cannot be compressed 

31. Manning Publications Giveaways
1. Serverless Applications with Node.js - Slobodan Stojanović & Aleksandar Simović
www.manning.com/books/serverless-applications-with-nodejs
2. Production-Ready Serverless - Yan Cui www.manning.com/livevideo/production-
ready-serverless
3. Serverless Applications with AWS - Marcia Villalba
www.manning.com/livevideo/serverless-applications-with-AWS
4. Serverless Architectures on AWS, 2nd Ed - Peter Sbarski
www.manning.com/books/serverless-architectures-on-aws
5. Voice Applications for Alexa and Google Assistant - Dustin Coates
www.manning.com/books/voice-applications-for-alexa-and-google-assistant
6. The Quick Python Book, Third Edition - Naomi Ceder www.manning.com/books/the-
quick-python-book-third-edition
7. Google Cloud Platform in Action - JJ Geewax [PRINT]
https://www.manning.com/books/google-cloud-platform-in-action