Third Meetup Slides Mulesoft Mexico City

Information about Third Meetup Slides Mulesoft Mexico City

Published on August 20, 2019

Author: AlanMuozOchoa

Source: slideshare.net

Content

1. Mule 4 What's new? Speaker: Fernando Silva

2. Introduction

3. All contents © MuleSoft Inc. Introductions 3 • Meet the speaker: Software Engineer (MuleSoft Developer) Experience on MuleSoft development life cycles in several projects in countries such as USA, Myanmar, Mexico, Panamá, and Venezuela using MuleSoft Anypoint Integration Solutions. Certified as MuleSoft Integration and API Associate, MuleSoft Certified API Design Associate (RAML 0.8), Solution Design Specialist and I participated in Anypoint Platform: Advance Developer Course and Anypoint Operations: Customer Hosted Runtimes

4. Mule 4 What's new? Speaker: Fernando Silva

5. All contents © MuleSoft Inc. Mule 4 5 • Simplified event and New message structure. • DataWeave 2.0 as the default simpler expression language. • Seamless streaming. • Better enrichment in fewer steps. • Smarter mule: Self-tuning runtime. • Simpler batch module. • Simplified Error handling. • Mule SDK. • Frictionless upgrades.

6. All contents © MuleSoft Inc. 6 New Message Structure

7. All contents © MuleSoft Inc. 7 Old event and message

8. All contents © MuleSoft Inc. New event and message 8 • Events have a message and variables. • Each message contains:  Payload.  Attributes. • Variables can any object:  Data  Attributes  Even another Message.  flowVars > vars  SessionVars X  outboundProperties X Message Event Payload Attributes Variable1 (Object) Variable2 (Message)

9. All contents © MuleSoft Inc. Attributes 9

10. All contents © MuleSoft Inc. 10 Dataweave 2.0

11. All contents © MuleSoft Inc. Dataweave 2.0 11 • Imports and modules. • Java interoperability. • New data formats. • Simplified syntax • New advanced capabilities.

12. All contents © MuleSoft Inc. Transformation and Data Simplified 12 • Formal type system defined. Types can be:  Binary.  CSV.  JSON.  XML.  Object (and sub types – List, Attributes, etc).  Scalar – Number, String, etc.

13. All contents © MuleSoft Inc. New Modules 13 • DataWeave Modules: • Core (dw::Core) • Arrays (dw::core::Arrays) • Binaries (dw::core::Binaries) • Encryption (dw::Crypto) • Diff (dw::util::Diff) • Objects (dw::core::Objects) • Runtime (dw::Runtime) • Strings (dw::core::Strings) • System (dw::System) • URL (dw::core::URL)

14. All contents © MuleSoft Inc. 14 Simpler Language

15. All contents © MuleSoft Inc. Dataweave 2.0 15 • Default transformation and expression language, replacing Mule Expression Language (MEL).

16. All contents © MuleSoft Inc. Mule 3 compatibility and MEL 16 • MEL is still around, it’s just deprecated. • Every expression can feature the “mel:” prefix to indicate that it should be evaluated with MEL.

17. All contents © MuleSoft Inc. 17 Seamless Streaming

18. All contents © MuleSoft Inc. Mule 3 Streaming 18

19. All contents © MuleSoft Inc. Seamless Streaming 19

20. All contents © MuleSoft Inc. Mule 3 Streaming 20 • Mule 4 introduces repeatable and concurrent streams:  The before scenario will work by default.  A stream can be consumed any amount of times in a flow. Concurrent stream consumption is also possible so that the multiple branches of a scatter-gather scope can each consume a stream the scope may receive on a flow.

21. All contents © MuleSoft Inc. Seamless Streaming 21 Mule 3 Streaming Complexity Mule 4 Seamless Streaming

22. All contents © MuleSoft Inc. 22 No more Message Enricher

23. All contents © MuleSoft Inc. Enrichment 23 • Directly output data into variables. • For other use cases, use transform to enrich.

24. All contents © MuleSoft Inc. 24 Self-tuning Engine Smarter Mule

25. All contents © MuleSoft Inc. Non-blocking execution engine 25 • Mule 4 now analyzes runtime conditions and makes adjustments automatically. • Achieves optimal performance without having to do manual tuning steps, such as:  Declaring exchange patterns.  Processing strategies  Threading configuration.

26. All contents © MuleSoft Inc. Non-blocking execution engine 26

27. All contents © MuleSoft Inc. 27 Simpler Batch Module

28. All contents © MuleSoft Inc. Batch module 28 • First introduced in Mule 3.5. • Process messages in batches. • Particularly useful when working with engineering “near real- time” data integration between SaaS applications.

29. All contents © MuleSoft Inc. Simpler Batch module 29 • Now the scope can live inside a flow. • We no longer have recordVars for batches. You can now use flow variables directly. This will save you bugs and undesired behavior. • Easier to understand.

30. All contents © MuleSoft Inc. 30 Simpler Error Handling

31. All contents © MuleSoft Inc. Error types: Part of every component 31 New error object that allows us to easily discover possible errors at a design level.

32. All contents © MuleSoft Inc. Error types: Hierarchy 32

33. All contents © MuleSoft Inc. Error handler 33 • Event Step in case of exception occurs at 2.

34. All contents © MuleSoft Inc. Simplified error handling and try scope 34 1. New try block (catch errors in the middle of a flow, no need to create a new flow for specific error fishing). 2.Simplified syntax when using transactions and error handling.

35. All contents © MuleSoft Inc. 35 Mule SDK

36. All contents © MuleSoft Inc. Mule SDK 36 The Mule SDK is the successor for Anypoint Connector Devkit. • Allows extending Mule runtime with your own modules and connectors. • No more generated code • Classloading isolation • Consistent connect experience

37. All contents © MuleSoft Inc. Migrating from DevKit 37 • Anypoint Connector DevKit is not compatible with Mule 4. • DevKit migration tool (https://docs.mulesoft.com/mule- sdk/v/1.1/dmt)  A new project will be generated which adapts your existing code into an SDK compatible Project (it will still require your review and adjustment)

38. All contents © MuleSoft Inc. 38 Frictionless upgrades

39. All contents © MuleSoft Inc. Classloader isolation 39 • Runtime, Anypoint Connectors and any library changes that occur internally do not affect the application itself. • Connectors are distributed outside the runtime as well, making it possible to get connector enhancements and fixes without having to upgrade the runtime or vice versa.

40. All contents © MuleSoft Inc. 40 Frequently Asked Questions

41. All contents © MuleSoft Inc. Frequently asked questions 41 • Is Mule 4 available in CloudHub? Yes! Mule 4 is already available and ready to deploy. • Is Studio 7 compatible with Mule 3.x? No. You must use Studio 6 to open 3.x projects. Similarly, if you want to deploy applications on Mule 4.0, you must compose those applications in either Anypoint Studio 7.0 or Anypoint Design Center - flow designer.

42. All contents © MuleSoft Inc. Frequently asked questions 42 • Can you run a 3.x app on 4.x runtime? No. There will be a migration tool available to assist with migrating apps currently running on Mule 3.x to Mule 4.x. • What tools will be available to assist in this migration? MuleSoft will release a migration tool integrated in Anypoint Studio 7 that will automatically update old configurations to use Mule 4 components (it will still require your review and adjustment).

43. Q&A

44. Thank you! See you next time.

45. 26 de julio, 2019. Third México City MuleSoft Meetup

46. All contents © MuleSoft Inc. What’s all about? 46 • A group from the community to the community. • A safe environment to learn and share your integration experiences both good and bad with your peers. • Discuss a variety of topics key to successful application network with MuleSoft Anypoint Platform.

47. Agenda

48. All contents © MuleSoft Inc. Agenda 48 • 08:00am: Introduction to Mule 4. • 9:15am: Debate • 9:45am: Q&A / Snack break. • 10:15am: Anypoint RTF • 11:00am: Custom Policies

49. Introductions

50. All contents © MuleSoft Inc. Introductions 50 • Meet the leader: • Studies in Computer Engineering. Started working with Mulesoft about a 3 years ago. Found my self very excited about the API and micro- services world. • Experience in different industries as. • Finnantial Services (Banking) • Fintechs • E-commerce • Mulesof trainer • Certifications: • API Design Associate • API Developer Associate • Courses: • Advanced Developer • Architecture: Application Networks • Architecture: Integration Solutions

51. All contents © MuleSoft Inc. Control and Automation Engineer (Mulesoft Technical Leader) Experience on MuleSoft development life cycles in several projects in countries such as Panama, Colombia, USA, Mexico, using MuleSoft Anypoint Integration Solutions. Certifications: • API Desing Associate • API Developer Associate Courses: • Anypoint Platform: API Design • Anypoint Platform: Development Fundamentals • Mulesoft.U Fundamentals • Muleosft.U Flow Design Introductions 51 • Meet the leader:

52. All contents © MuleSoft Inc. Introductions 52 • Conoce a los participantes: • What’s your name? • What do you do? • What have been your experience?

53. All contents © MuleSoft Inc. 53 Snack break time! … and picture time!

54. Anypoint Runtime Fabric Speaker: Alan Muñoz

55. All contents © MuleSoft Inc. 55 Runtime Plane

56. All contents © MuleSoft Inc. Runtime Plane 56

57. All contents © MuleSoft Inc. 57

58. All contents © MuleSoft Inc. Anypoint Runtime Fabric 58 Anypoint Runtime Fabric

59. All contents © MuleSoft Inc. 59 Anypoint Runtime Fabric

60. All contents © MuleSoft Inc. Deployment Types 60

61. All contents © MuleSoft Inc. Runtime Plane Comparisson 61

62. Q&A

63. Gateway Polices Speaker: Jose Antonio Escobar Macias

64. All contents © MuleSoft Inc. About the speaker 64 • I have been working with Mulesoft about 2 years, I fell in love with APIs and Microservices, Cloud Computing and Integration.​ • I have been enrolled in projects to make the implementation and management of APIs in private bank and food company.​ • I got the certifications of API Associate in Mule 3.7 and API Design RAML 1.0. • It´s my first presentation in a Mule meetup, so, LETS DO IT!

65. All contents © MuleSoft Inc. What is an API Gateway? 65 An API Gateway is just that a gateway protecting APIs. We must face to main issues when we expose an API: •Security •Performance API Gateways solve these problems by implementing standard management, encryption and authentications giving API developers a way to let people in and direct them to the right place. Gateways serve as a point of control over APIs, determining which traffic is authorized to pass through the API to backend services, to meter the traffic flowing through, to log all transactions and to apply runtime policies to enforce governance like rate limiting, throttling and caching.

66. All contents © MuleSoft Inc. What is a Gateway Policy 66 Policies are the tool to apply orthogonal behavior to a whole API or to a resource of it. A policy extends the functionality of an API and enforces certain capabilities such as security. A policy can control access and traffic. You can create policies to enrich, filter, and control Incoming/Outgoing messages, and to apply a security layer on top of your API by, for example, enforcing token access to your API or whitelisting/blacklisting specific IP addresses.

67. All contents © MuleSoft Inc. Mule Policies 67 • Categories: – Compliance​ – Security​ – Quality of Service​ – Transformation​ – Troubleshooting • Default Polices:

68. All contents © MuleSoft Inc. Custom Policies in Mule 3 vs Mule 4 68 MULE 4​ MULE 3​ MEL expressions are replaced by DataWeave.​ Processor Chain and MEL Expressions are useful for validations​ In Mule 4, policies are no longer separated ina before and after block. They now work as a flow with an explicit jump to the next policy or flow that has to be defined in it.​ In 3.x, the logic inside a particular policy is split in two blocks, one that is executed before the next policy or flow, the other executed after it.​ Pointcut elements are no longer defined in the policy config file. Now, they are resolved by the API Gateway when policies are fetched from API Manager.​ You must define a “poincut” <pointcut><api-platform- gw:api- pointcutapiName="sampleApi"apiVersi on="1.0.0"/></pointcut> to matchthe G ateway Policy tothe APIImplementatio n.​

69. All contents © MuleSoft Inc. Mule 3 vs Mule 4 in Custom Policy 69

70. All contents © MuleSoft Inc. Important Info 70 • YAML Definitions: Name  string - Policy name Description  string - A description that displays in the policy details when applying it Category string - Category of the policy Standaloneboolean - True if the policy can work on its own or false if the policy can be applied only as part of another policy. Configuration  array - A set of configurable properties associated with your policy, details on the parameters for each property below. resourceLevelSupported  boolean - True means the user can apply the policy to specific API resources; False means the policy applies to all API resources. (Mule 3.8.1 and later) • Important Considerations You can create a custom policy if you use one of the following runtimes: – Mule 3.8 or later unified runtime – API Gateway runtime 2.x or later • Studio 6.1 or Later • You create a custom policy by using the elements in Mule Runtime to evaluate and process HTTP calls and responses. • To import a policy you need the YAML and XML FILE • The DataWeave component is supported for use within Custom Policies on Mule Runtime 3.8.5 and later. • YAML Properties are invoked like this {{propertyName}} • If you want to execute the policy in an order Set the order to an integer greater than 2 because the order values 0 - 2 are reserved for CORS, Throttling, and Rate Limit policies

71. All contents © MuleSoft Inc. Important Info 71 • About the performance

72. Lets do the practice!

73. Q&A

74. All contents © MuleSoft Inc. What’s next? 74 • Share: – Tweet your pictures with the hashtag #MuleMeetup – Invite your network to join: https://meetups.mulesoft.com/mexico- city/ – Contact your organizer at [email protected] to suggest topics – Contact MuleSoft at [email protected] for ways to improve the program • Our next meetup: – Date: Planning… – Location: What do you think about the current space? – Topic: What would you like to talk about in the next meeting?

75. Thank you! See you next time.

#mulemeetup presentations

Mumbai MuleSoft Meetup 13
12. 09. 2020
0 views

Mumbai MuleSoft Meetup 13

Mumbai MuleSoft Meetup 12
02. 08. 2020
0 views

Mumbai MuleSoft Meetup 12

Mumbai MuleSoft Meetup 11
14. 06. 2020
0 views

Mumbai MuleSoft Meetup 11

Related presentations