Wenn. Schnittstellen. alt werden... Claus Straube IT Architekt

Größe: px

Ab Seite anzeigen:

Download "Wenn. Schnittstellen. alt werden... Claus Straube IT Architekt"

Imke Emilia Hartmann
vor 6 Jahren
Abrufe

1 Wenn Schnittstellen alt werden... Claus Straube IT Architekt

2 A B Provider Consumer

3 Request A Response B Provider Consumer

4 Payload Request A Response B Provider Consumer

5 Payload Request A Response B Provider Consumer

6 Payload Request A Response B Provider Consumer

7 Payload Request A Response B Provider Consumer

8 Payload Request A Response B Provider Consumer

9 Payload Request A Response B Provider Consumer

10 Payload Request A Response B Provider Consumer

11 Payload Request A Response B Provider Consumer

12 B kennt A B kennt die Payload Struktur von A Request A Response B Provider B kennt die Struktur von A Consumer

13 System B muss ziemlich viel von System A kennen, damit die Kommunikation funktioniert!

14 Payload Request WARUM A Response B Provider Consumer

15 Payload Request A Response B Provider Consumer

16 Evolution

17 Evolution 2.0

19 Technical Dept

20 Payload Request A Response B Provider Consumer

21 B kennt A B kennt die Payload Struktur von A Request A Response B Provider B kennt die Struktur von A Consumer

RestBucks, the sample http://codebetter.

22 RestBucks, the sample in practice the book restbucks the sample restbucks of hypermedia/

25 Request A Response B Provider B kennt die Struktur von A Consumer

26 v1/ create_ order

27 create_ order

28 v2/ order/{ id} POST = create order PATCH = update order DELETE = delete order GET = read order

29 Kunde Hi Hallole Barista

30 Schritt 1 Schritt 2 Schritt 3 update order order pay order prepare order cancel order

31 Schritt 4 Schritt 5 completed drink

32 Hateoas Hypermedia As The Engine Of Application State

33 Schritt 1 Request Response self GET: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} order POST: RESTBUCKS.io/v2/order update_order POST/PATCH: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} cancel_order DELETE: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} pay_order PUT: RESTBUCKS.io/v2/order/1/payment RESTBUCKS.io/v2/order/{id}/payment

34 Schritt 1 Request Response self GET: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} order POST: RESTBUCKS.io/v2/order update_order POST/PATCH: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} cancel_order DELETE: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} pay_order PUT: RESTBUCKS.io/v2/order/1/payment RESTBUCKS.io/v2/order/{id}/payment

35 Schritt 2 Request Response update order PATCH: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id}

36 Schritt 2 Request Response self GET: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} update order PATCH: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} update_order POST/PATCH: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} cancel_order DELETE: RESTBUCKS.io/v2/order/1 RESTBUCKS.io/v2/order/{id} pay_order PUT: RESTBUCKS.io/v2/order/1/payment RESTBUCKS.io/v2/order/{id}/payment

37 B kennt A B kennt die Payload Struktur von A Request A Response B Provider B kennt die Struktur von A Consumer

38 B kennt A Request A Response B Provider Consumer

39 B kennt A Request A Response B Provider Consumer

40 A Message Broker B Provider Consumer

41 Message Broker A? B Provider Consumer

42 Schritt 1 Schritt 2 Schritt 3 update order order pay order prepare order cancel order

43 Schritt 1 Schritt 2 Schritt 3 update order event order event pay order event prepare order event cancel order event

44 FooEvent Listener SomeEvent Listener BarEvent Listener SomeEvent Listener Message Broker A FooEvent Topic BarEvent Topic B SomeEvent Topic Provider Consumer

45 B kennt A B kennt die Payload Struktur von A Request A Response B Provider B kennt die Struktur von A Consumer

46 B kennt die Payload Struktur von A A Response B Request Provider Consumer

47 1 Kaffee ohne Milch 2 Kaffee mit Milch

48 Order LineItem 1 Kaffee ohne Milch 2 Kaffee mit Milch

49 Order 1 1..* LineItem Name : String Quantity : int Milk : Boolean Size : Size

50 Schema Evolution

53 Writer Reader

54 Writer Order Schema {JSON} V1.0 V1.0

55 Writer Order Schema {JSON} V1.0 V1.0 Reader Order Schema {JSON} V1.0 V1.0

56 Version 1.0 [ ] { "namespace": "de.muenchen.jfs17", "type": "record", "name": "LineItem", "fields": [ {"name": "name", "type": "string", "default": "coffee"}, {"name": "quantity", "type": "int", "default": "1"}, {"name": "milk", "type": "boolean", "default": "false"} ] }, { "namespace": "de.muenchen.jfs17", "type": "record", "name": "Order", "fields": [ {"name": "item", "type": "LineItem"} ] }

57 Version 1.0 [ { "namespace": "de.muenchen.jfs17", "type": "record", "name": "LineItem", "fields": [ {"name": "name", "type": "string", "default": "coffee"}, {"name": "quantity", "type": "int", "default": "1"}, {"name": "milk", "type": "boolean", "default": "false"} ] }, { "namespace": "de.muenchen.jfs17", "type": "record", "name": "Order", "fields": [ {"name": "item", "type": "LineItem"} ] } LineItem Type ]

58 Version 1.0 [ { "namespace": "de.muenchen.jfs17", "type": "record", "name": "LineItem", "fields": [ {"name": "name", "type": "string", "default": "coffee"}, {"name": "quantity", "type": "int", "default": "1"}, {"name": "milk", "type": "boolean", "default": "false"} ] }, { "namespace": "de.muenchen.jfs17", "type": "record", "name": "Order", "fields": [ {"name": "item", "type": "LineItem"} ] } Order Type ]

59 Servus Hallole

60 Writer Order Schema {JSON} V2.0 V2.0

61 Writer Order Schema {JSON} V2.0 V2.0 Reader Order Schema {JSON} V1.0 V1.0

62 Writer Reader Neu Neu Alt Alt Vorwärtskompatibilität

63 Writer Reader Alt Alt Neu Neu Rückwärtskompatibilität

64 Version 2.0 [ { "namespace": "de.muenchen.jfs17", "type": "enum", "name": "Sizes", "symbols": ["LARGE", "MIDDLE", "SMALL"] }, { "namespace": "de.muenchen.jfs17", "type": "record", "name": "RechnungsPosten", "aliases": ["LineItem"], "fields": [ {"name": "name", "type": "string", "default": "coffee"}, {"name": "quantity", "type": "int", "default": "1"}, {"name": "milk", "type": "boolean", "default": "false"}, {"name": "size", "type": "Sizes", "default": "MIDDLE"} ] }, { "namespace": "de.muenchen.jfs17", "type": "record", "name": "Bestellung", "aliases": ["Order"], "fields": [

65 Schema Server Order Schema {JSON} V2.0 V2.0 Order Schema {JSON} V1.0 V1.0 1 gr. Kaffee ohne Milch 2 kl. Kaffee mit Milch

66 Schema Server Order Schema {JSON} V2.0 V2.0 Order Schema {JSON} V1.0 V1.0 A Message Converter Message Broker OrderEvent Topic Message Converter B

67 Schema Server GET /{subject}/{format} Order Schema {JSON} V2.0 V2.0 Order Schema {JSON} V1.0 V1.0 GET /{subject}/{format} A Message Converter Message Broker OrderEvent Topic Message Converter B

68 Schema Server GET /{subject}/{format} Order Schema {JSON} V2.0 V2.0 Order Schema {JSON} V1.0 V1.0 GET /{subject}/{format} A Message Converter Avro Message Message Broker OrderEvent Topic Avro Message Message Converter B

69 Schema Server GET /{subject}/{format} Order Schema {JSON} V2.0 V2.0 Order Schema {JSON} V1.0 V1.0 GET /{subject}/{format} A Message Converter Avro Message Message Broker OrderEvent Topic Avro Message Message Converter B cloud stream/

71 DEMO

73 Herzlichen Dank Für die Aufmerksamheit! Claus Straube Landeshauptstadt München Agnes Pockels Bogen

Ähnliche Dokumente

SODA. Die Datenbank als Document Store. Rainer Willems. Master Principal Sales Consultant Oracle Deutschland B.V. & Co. KG

SODA. Die Datenbank als Document Store. Rainer Willems. Master Principal Sales Consultant Oracle Deutschland B.V. & Co. KG SODA Die Datenbank als Document Store Rainer Willems Master Principal Sales Consultant Oracle Deutschland B.V. & Co. KG vs No Anforderungskonflikte Agile Entwicklung Häufige Schema-Änderungen Relationales