Serverless platforms are rapidly gaining adoption and for good reason - it’s a consumable and cost-effective way to host functions and capabilities. Developers are told they simply need to write code and let the platform take care of the rest. However, it’s not always that straight-forward; most applications in production are complex and have restrictions to integrate with legacy systems. In this talk, we’ll cover the hybrid architectures that result from refactoring existing applications for modern workloads. In addition, we’ll consider requirements that developers encounter when going to production like security and analytics for APIs. We’ll tackle how serverless allows you to transform your applications from traditional to modern hybrid architectures.

1. BUILDING SERVERLESS APIS
FOR MODERN ARCHITECTURES
SAI VENNAM - DEVELOPER ADVOCATE - IBM
@sai_vennam

2. Traditional
on-premise

3. Traditional
on-premise
‣ Powerful and full-featured
‣ Often large and clunky
‣ Hard to scale efficiently
‣ Generally all a single language
‣ Difficult to onboard devs

4. Cloud-Native
Modern

5. Cloud-Native
Modern
‣ Powerful and full-featured
‣ Effective at all scales
‣ Easy to scale individual components
‣ Promotes agile development
‣ Choose the right language for the job

6. Cloud-Native
Modern
Traditional
on-premise
?

7. Hybrid Architecture

8. Scenario

9. What exactly is serverless?

10. DEMO

11. WITHOUT API MANAGEMENT

12. WITH API MANAGEMENT
APIGateway

13. DEMO

14. HYBRID ARCHITECTURE - STEPS IN THE RIGHT DIRECTION
Learn more about Acme Freight at github.com/IBM/acme-freight

15. Thanks! Questions?
@sai_vennam