Serverless Swift with Apache OpenWhisk

James Thomas
Developer Advocate at IBM, UK

Do you want to build backend applications using Swift but don't want to manage computing infrastructure to run those applications in the cloud? Enter serverless cloud platforms… 

These services allow developers to push code, rather than VMs, into the cloud. The platforms allow you to connect external event sources like API requests or message queues to functions in your code. As events occur, your code is instantiated and executed to process each request. Developers are only billed for the milliseconds needed to process each request.

In this session, developers will learn how to build Swift microservices using modern “serverless” cloud platforms. We’ll look at common challenges (and solutions) to building applications using “serverless” stacks. Exploring emerging “serverless” design patterns will give developers the knowledge to build application architectures using these new platforms.

My talk will be split into three sections:

  1. An introduction as the background of serverless computing platforms. What are they, why would you use them and what benefits do they bring over other cloud technologies likes IaaS, Containers or Paas. 
  2. The middle is then a "live coding" session using one of these platforms to build a real Swift backend application (serverless apis to create a slackbot) to show developers the techniques and skills for building serverless applications through a real world demonstration. I'll build the application, deploy to the cloud and get it running in under twenty minutes from scratch.
  3. Finally, I finish looking at the challenges of serverless development today. What are the difficulties? Monitoring, debugging, etc.... and introduce some workarounds or solutions. 


About speaker

James is a “Developer Advocate” for IBM, helping developers build scalable applications on IBM's cloud platform. Having accepted a summer-long internship with IBM as “something to do” before starting his post-graduate degree, James is still here eight years later. Managing to find his way into the “Emerging Technologies” division, James has been able to work on everything from the largest retail banking site in Europe, been a leading open-source developer for a JavaScript toolkit before working on the first commercial system for IBM Watson as the UI Technical Lead.
All topics