Serverless architectures with Fn Project

Transcription

1 überraschend mehr Möglichkeiten! Serverless architectures with Fn Project s Sven Bernhardt, Danilo Schmiedel OPITZ CONSULTING 2018

2 OPITZ CONSULTING - A success story since 1990 Our Mission: Help organizations to leverage the possibilities of digitalization to be different, better and faster than their competitors Owner-led company with 450+ consultants 11 locations in Germany and Poland About us Danilo Schmiedel Sven Bernhardt Senior Managing Consultant Business Development and Innovation Senior Solution Architect Technical Lead for API Management OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 2

3 Agenda Serverless, FaaS, BaaS Fn Project Fn Flow 4 Use Cases and Scenarios 5 Summary OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 3

4 Serverless, FaaS and BaaS 1 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 4

5 Serverless standard picture Serverless!= No Server => Just means someone else s computer Serverless = Exit door from traditional IT operations, since no Servers are needed anymore? Clearly no! Serverless just mean that your code is running on someone elses computer somewhere, somehow and you don t have to care about it. OPITZ CONSULTING 2018 Serverless architectures with Fn Project Source: Seite 5

6 Promises of Serverless Easier: Just think about your code, not infrastructure Powerful: Transparent and limitless scaling Faster: Deploy faster, iterate faster, innovate faster Cheaper: Only pay for what you use (never idle) Source: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 6

7 Serverless Manifesto by Potes & Nair (AWS) Functions are the unit of deployment and scaling No machines, VMs, or containers visible in the programming model Permanent storage lives elsewhere Scales per request: Users cannot over- or under-provision capacity Never pay for idle (no cold servers/containers or their costs) Implicitly fault-tolerant because functions can run anywhere BYOC Bring Your Own Code Metrics and logging are a universal right OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 7

8 Characteristics of a Function Granular compute unit in Serverless Short-lived Ephemeral Stateless Scalable Event-Driven Single Purpose Self-contained Function has one output for a specific input Input x Function f Output f(x) OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 8

9 Serverless, FaaS and BaaS Serverless: Abstraction of infrastructure and its operations including provisioning, scaling, patching, etc. Serverless applications significantly depend on third-party services A Serverless Computing Platform may provide one or both of: Functions-as-a-Service: Compute component in a serverless platform Custom Code that runs in ephemeral containers Backend-as-a-Service: Third-party API-based services Replaces core subsets of functionality in an application OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 9

10 Evolution of application architectures Monolithic architectures µservice architectures Serverless architectures f(a 1 ) f(a 2 ) f(b 1 ) f(b 2 ) f(a 3 ) f(a 4 ) f(b 3 ) f(b 4 ) f(c 1 ) f(c 2 ) f(d 1 ) f(d 2 ) f(c 3 ) f(c 4 ) f(d 3 ) f(d 4 ) Single application Mixed data from different business context Mixed business logic Application consists of different µservice Business logic and data belong to a bounded business context Application consists of multiple functions Fine-granular logic for a specific step, data resides externally OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 10

11 Serverless: Focus on implementing business logic OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 11

12 Serverless and Cloud-Native technologies Source: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 12

13 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Source: Seite 13

14 Fn Project 2 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 14

15 About Fn Project Open-source Functions-as-a-Service compute platform (Apache 2.0 licence) Easy to use for developers Easy to manage for operators Active large core team, commits, 75+ contributors Members on the CNCF serverless working group Native CloudEvents support ( Specification for describing event data in a common way Event declaration and delivery across services and platforms OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 15

16 Fn Project architecture Written in Go Container-based: Leverages Docker Run anywhere: Cloud On-Premise Datacenter Local development environment OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 16

17 Fn Project runtime Fn is runtime-agnostic Can be targeted to run on Kubernetes (K8s) K8s optimizations are WIP Plans for deeper K8s integration using CRDs Helm chart available to install to K8s ( Runtime monitoring: Prometheus support for metrics collection Metrics visualization with Grafana OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 17

18

19 Wait! Functions and Containers... What the heck? Serverless Manifesto says: No machines, VMs, or containers visible in the programming model So Fn Project is not really Serverless, right? Fn is FaaS, the underlying platform needs to ensure that Developer does not need to care about the containers and the technical stuff belonging to it (Build, Deploy, Run...) Users does not need to pay for idle containers Function is capable to scale automatically and infinitetly Advantage of the container-based approach is increased iteroperability (no vendor lock-in) Other Container-based FaaS Frameworks: Kubeless, Fission OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 19

20 Function development Multi language support through Function Developer Kit (FDK) FDKs comprise of different building blocks, like Language-specific Fn libraries Build-Time Docker images Minimal runtime Docker images Fn CLI is used to manage and create Functions OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 20

21 Serverless Manifesto and Fn Project Functions are the unit of deployment and scaling No machines, VMs, or containers visible in the programming model Permanent storage lives elsewhere Scales per request: Users cannot over- or under-provision capacity Never pay for idle (no cold servers/containers or their costs) Implicitly fault-tolerant because functions can run anywhere BYOC Bring Your Own Code Metrics and logging are a universal right OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 21

22 Demo - Function development OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 22

23 Fn Flow 3 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 23

24 Building advanced functions with Fn Flow Build reliable and scalable FaaS applications with functions Flow functions are written purely in code Build distributed applications Provides rich concurrency primitives including fork-join, chaining, delays and error handling Testable using standard programming tools and mechanisms (e.g. Unit tests) OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 24

25 Fn Flow compared to workflow solutions No context-switching, beause everything is code Leverage full power of the used programming language More powerful errorhandling capabilities Easy, consistent and comprehensible data and context handling Highly functional approach for implementing the flow Might be hard to read and understand for non-technicians OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 25

26 Example Use Case Fn Flow: Saga Microservice Pattern: Saga defined by Chris Richardson Specifically: Orchestration-based Saga Source: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 26

27 Source: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 27

28 Use Cases and Scenarios 4 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 28

29 10 common use cases for Serverless platforms OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 29

30 Serverless Best Practices 1. Each function should do only one thing 2. Functions don t call other functions 3. Use as few libraries in your functions as possible 4. Avoid using connection based services (use services rather than connections) 5. One function per route (if using HTTP) 6. Learn to use messages and queues 7. Data flows, not data lakes 8. Just coding for scale is a mistake, you have to consider how it scales (c) Paul Johnsten, ServerlessDays CoFounder OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 30

31 Severless & Enterprise Integration Patterns (EIP) EIPs try to address integration problems based on messaging In EIPs there are definitions for basic components that are used to implement integrations, like Channels Splitter Aggregator Router Source: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 31

32 Example: EIP Message Translator X System A System B f(x) getdata f(x) transformdata f(x) senddata OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 32

33 Example: EIP Message Splitter and Router System B f(x) routedatatob System A System C f(x) getdata f(x) splitdata f(x) routedatatoc OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 33

34 When is FaaS adequate for integration? Typical use cases: Batch processing, which takes place on regular schedules Event processing Considerations to make: Number of invocations Keep runtime short Serverless Platforms will terminate long-running Functions Don t block HW resources for too long OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 34

35 Summary 5 OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 35

36 Summary Functions are first class citizens Fn Project is a Framework for implementing FaaS-style applications But is not a Serverless framework (no Serverless runtime available) FaaS is good for the right use cases, but it s no silver bullet! Strength of Fn Project: No vendor lock-in! FaaS provides new opportunities for implementing applications Event-based, scalable and ephemeral Stateless Infinitely scalable (in theory) OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 36

37 With great power, comes great responsibility... Rethink the traditional application architectures! API Gateway POST /api/v1/orders GET /api/v1/products PlaceOrder OrderCreated Event Hub Client OrderCreated OrderCreated SearchProducts IDM / Authentication CheckoutWarehouse CreateInvoice OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 37

38 Links and Resources Fn Project: Github Fn Project: CNCF Whitepaper Serverless: CloudEvents: Enterprise Integration Patterns: Microservices Patterns: OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 38

39 Q & A OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 39

40 überraschend mehr Möglichkeiten! Contact us! Danilo Schmiedel Senior Managing Consultant Solutions Oracle ACE Director OPITZ CONSULTING Deutschland GmbH Tempelhofer Weg 64, Berlin, Germany Phone: Sven Bernhardt Senior Solution Architect Oracle ACE OPITZ CONSULTING Deutschland GmbH Kirchstrasse 6, Gummersbach, Germany Phone: OPITZCONSULTING opitzconsulting OPITZ CONSULTING 2018 Serverless architectures with Fn Project Seite 40