Many of us agree that adopting serverless in an enterprise has challenges. These challenges increase when the enterprise has no serverless expertise within itself. We know that serverless requires a new mindset and a different way of approaching application development. When business pressure mounts to deliver solutions faster, organisations often fall into the trap of quickly building a team by pulling engineers from different sources in order to satisfy the business goals. What such quick-fix solutions fail to achieve is the basic growth of the serverless knowledge and skills of its employees. Thus, the serverless adoption challenges left unattended.
For a company that credits its own growth on the growth of its people, these quick-fix approaches are not going to offer much help. For a long term gain and to develop a growth culture within the organisation, it is important to recognise the uplift of its serverless expertise. This is where organically growing a serverless team becomes beneficial.
In this talk, taking inspiration from the nature, I will take you through few important phases of growing a serverless team, and discuss how it can bring near term as well as long term benefits to an organisation. Let’s all grow and not build a serverless team!
10. Early adoption
Endless experimentation
start simple iterate, evolve
follow proven patterns
solution first;
perfection next
continuous
improvement
judgmental
can’t take risk
vendor lock-in fear
invest in expansive
processes
wait for a perfect
moment
11. To Endless Experiments
Pressure
• Internal stakeholders
• External competition
Status
• Maintaining the image
• Legacy tech stack
Customer
• Modern demands
• Loosing loyalty
28. Serverless Mind
Serverless requires a "mind-shift" to see the
products as event-driven orchestration of
managed services, knitted with infrastructure
code, to bring the best value
33. Serverless Engineer
“A software engineer who is innovative,
efficient, capable of building secure, cloud
first and cost effective functional solutions
iteratively using managed services.”
44. • Parallel development streams
• MVP first, sophistication next
Fast features
• Automated deployment pipeline
• Multiple daily releases
Rapid releases
• Confidence in the technology
• Trust in the teams
Business
harmony
46. Serverless requires a new way of thinking, new way of
working, and new way of running applications. Meaning,
we need to change our way of thinking, our way of
working, and our way of running applications.
Serverless Thinking
49. helps to grow high
calibre serverless
competency
helps to keep the tech
stack fresh and
efficient
saves from expensive
and complex legacy
migration cycles
aids to build a secure,
resilient and scalable
ecosystem
50. If serverless can be the slingshot to give us the
acceleration to win battles and bring value, then
we must accept, adopt and of course, accelerate
to enjoy the true potential of being serverless!
To close…