Successfully reported this slideshow.
Your SlideShare is downloading. ×

Manila MuleSoft Meetup #4 January 2019

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 88 Ad
Advertisement

More Related Content

Slideshows for you (20)

Similar to Manila MuleSoft Meetup #4 January 2019 (20)

Advertisement

Recently uploaded (20)

Manila MuleSoft Meetup #4 January 2019

  1. 1. January 31, 2019 : Journey to Success with Mule Manila MuleSoft Meetup #4
  2. 2. All contents © MuleSoft Inc. Our Partners 2
  3. 3. All contents © MuleSoft Inc. Selfie Time 3 Share Your Pictures • Tweet your pictures with the hashtag #ManilaMuleSoftMeetup #MuleSoftMeetup
  4. 4. Agenda
  5. 5. All contents © MuleSoft Inc. Agenda 5 • 6:30 pm: Registration, arrivals, food and drink • 7:15 pm: Introduction • 7:25 pm: Journey to Success with Mule • 7:45 pm: API Design • 8:25 pm: Networking time, games, food and drink • 8:55 pm: Wrap up
  6. 6. Introductions
  7. 7. All contents © MuleSoft Inc. Organizers 7
  8. 8. All contents © MuleSoft Inc. Speaker 8 Manila MuleSoft Meetup Organizer and WhiteSky Labs Senior Integration Consultant. He has been part of the IT industry for 10 years with 6 years of extensive experience in JAVA. He has worked with companies such as HP, Daimler and BDO. His mission is to build MuleSoft community here in the Philippines by sharing his experience and knowledge with fellow like-minded Mule enthusiasts.
  9. 9. All contents © MuleSoft Inc. Speaker 9 Greg has been working in the IT industry for 4 years. He is currently working as an Integration Consultant at WhiteSky Labs, providing digital transformation for top companies around the world. His expertise mainly focused in banking solutions and full stack development.
  10. 10. All contents © MuleSoft Inc. Introductions 1 0 Who are new in MuleSoft Meetup? Introduce Yourself • Name • Background • Experience in Mule
  11. 11. By Christopher Co Journey to Success with Mule
  12. 12. All contents © MuleSoft Inc. Topics • Challenges in Integration Space • Microservices and APIs • MuleSoft Products and Licensing
  13. 13. All contents © MuleSoft Inc. Introduction 13
  14. 14. All contents © MuleSoft Inc. In an Alternate Universe Far Far Away… Characters used in this presentation are copyright of DreamWorks Animation
  15. 15. All contents © MuleSoft Inc. Characters used in this presentation are copyright of DreamWorks Animation
  16. 16. All contents © MuleSoft Inc. 16 HOPPY Characters used in this presentation are copyright of DreamWorks Animation
  17. 17. All contents © MuleSoft Inc. 17Characters used in this presentation are copyright of DreamWorks Animation
  18. 18. All contents © MuleSoft Inc. Customers Are Evolving 18 I will just have to wait 2 weeks for my dress I want my beautiful dress NOW! Characters used in this presentation are copyright of DreamWorks Animation
  19. 19. All contents © MuleSoft Inc. Higher Customer Expectation 19 Customers Demand - More Speed - More Service Characters used in this presentation are copyright of DreamWorks Animation
  20. 20. All contents © MuleSoft Inc. Market New Entrants 20 Startups - Hyper Agile - Hyper Fluid - Can Pivot on a Dime Characters used in this presentation are copyright of DreamWorks Animation
  21. 21. All contents © MuleSoft Inc. Harder to Get Partners 21 New Partnership Opportunities are being lost because of a Lack of Easy API Integration Characters used in this presentation are copyright of DreamWorks Animation
  22. 22. All contents © MuleSoft Inc. Increasing Demand: New Products and Services 22
  23. 23. All contents © MuleSoft Inc. Point to Point Architecture 23
  24. 24. All contents © MuleSoft Inc. Point to Point Architecture 24 ● Difficult to Maintain ● No Reuse ● Costly ● Not Scalable ● Restriction of Technology Stack
  25. 25. All contents © MuleSoft Inc. 735 Stores Closed TROLL
  26. 26. All contents © MuleSoft Inc. 26 Characters used in this presentation are copyright of DreamWorks Animation
  27. 27. All contents © MuleSoft Inc. Meet Max the Mule 27Characters used in this presentation are copyright of DreamWorks Animation
  28. 28. All contents © MuleSoft Inc. 28
  29. 29. All contents © MuleSoft Inc. Indirect Competitors 29
  30. 30. All contents © MuleSoft Inc. New Partnerships 30
  31. 31. All contents © MuleSoft Inc. MicroServices 31 • https://www.youtube.com/watch?v=SouNISAnXlo Characters used in this presentation are copyright of DreamWorks Animation
  32. 32. All contents © MuleSoft Inc. API 32 Think of API as a contract of actions for requesting a service.
  33. 33. All contents © MuleSoft Inc. API-Led Connectivity 33
  34. 34. All contents © MuleSoft Inc. API-Led Connectivity 34
  35. 35. All contents © MuleSoft Inc. Application Network 35
  36. 36. All contents © MuleSoft Inc. Application Network Platform 36 • 1600+ enterprises use Anypoint Platform to build an application network to accelerate development by 3x.
  37. 37. All contents © MuleSoft Inc. Design your APIs 37 Anypoint Design Center ● Build Integration Flows ● Design APIs with RAML ● Reuse API Fragments
  38. 38. All contents © MuleSoft Inc. Share your APIs 38 Anypoint Exchange • Save • Share • Discover • Reuse
  39. 39. All contents © MuleSoft Inc. Manage your APIs 39 Anypoint Management Center • Manage Users • Performance Monitoring • Analyze Traffic • Monitor SLAs
  40. 40. All contents © MuleSoft Inc. Secure your APIs 40 • Secure Your Data • Control Access • Defend Critical APIs • Basic Auth • OAuth 2.0 • XML Threat Protection • Many more...
  41. 41. All contents © MuleSoft Inc. Mule Runtime Engine 41
  42. 42. All contents © MuleSoft Inc. What does Anypoint Design Center do? 42 • A. Design APIs with RAML • B. Reuse API Fragments • C. Build Integration Flows • D. All of the Above
  43. 43. All contents © MuleSoft Inc. Question What is the architectural design that structures an application into a collection of loosely coupled services which allows organizations to achieve agility and realize lower cost? A. Mule B. APIs C. Point to Point architecture D. Microservices
  44. 44. All contents © MuleSoft Inc. Anypoint Platform Plans 44
  45. 45. All contents © MuleSoft Inc. Platinum Plan
  46. 46. All contents © MuleSoft Inc. Titanium Plan
  47. 47. All contents © MuleSoft Inc. Got Questions on Anypoint Platform Plan? https://www.mulesoft.com/anypoint-pricing
  48. 48. All contents © MuleSoft Inc. Customers 48
  49. 49. All contents © MuleSoft Inc. ASICS Speeds Up IT Project Delivery by 2.5x 49 “One of the most difficult parts of development is creating connections. We can waste hours and hours on these tasks. Instead, Anypoint Platform connects all these different systems, making developers' lives easier.” Phil Connaughton, Director of Engineering, ASICS Digital
  50. 50. All contents © MuleSoft Inc. 50 “At JetBlue, we’re focused on humanizing the travel experience and rethinking our approach to customer service, including deploying mobile payments and being the first airline to roll out onboard purchases using Apple Pay. The tokenization capabilities within MuleSoft’s Anypoint Platform allow us to secure credit card transactions flowing through JetBlue eCommerce Platform, so that we can drive innovation and agility without compromising security.” Vitaly Faida Manager of IT Product Release Engineering, JetBlue
  51. 51. Questions?
  52. 52. All contents © MuleSoft Inc. Yeah yeah yeah… All of that sounds great. But… 52 Characters used in this presentation are copyright of DreamWorks Animation
  53. 53. API Design
  54. 54. All contents © MuleSoft Inc. Topics • Anypoint Platform – API fragment & libraries – RAML specification, versioning and raml dependencies as maven dependencies – https://raml.org/
  55. 55. All contents © MuleSoft Inc. API Designer • Introduction • Demo • Q&A
  56. 56. All contents © MuleSoft Inc. API Design • Who’s gonna be using the API? • Who are the end users? • What’s the purpose of the API? • What type of API are we building? Why? • How are we going to maintain the API? • How are we going to document the API?
  57. 57. All contents © MuleSoft Inc. API Design – Done?
  58. 58. All contents © MuleSoft Inc. API Design • How are we going to let developers interact with the API? • How are we going to manage authentication, provisioning, throttling, and security? • How are we going to manage support? Or are we going to even manage support?
  59. 59. All contents © MuleSoft Inc. API Design – Build a prototype
  60. 60. All contents © MuleSoft Inc. API Design – Problems
  61. 61. All contents © MuleSoft Inc. Introduction of RAML Specification • RESTful API Modeling Language • RAML enables developers define their API with tools to design, prototype, document and allow user interaction. • RAML was designed to encompass the entire API Lifecycle RAML was designed to encourage careful design and code reusability (Resource Types, Traits, Data Types, Examples) • Based on YAML, RAML is designed to be human readable (meaning even non- programmers can read and edit it)
  62. 62. All contents © MuleSoft Inc. Spec Driven Development • Define your API before coding • Reuse Codes • Mock and get User Feedback • Make Necessary Changes • Start Coding
  63. 63. All contents © MuleSoft Inc. Advantage of RAML • RAML will let you see what your API looks like as you design it, using easy to read plain text. • Let’s you define your API with only a few lines of code. • You can easily make changes on your API whether it’s the design or documentation. • You can let your customers, partners, or even your own internal engineers interact with the mocked out API to either review and build off of.
  64. 64. All contents © MuleSoft Inc. Demo - Creating RAML Specification
  65. 65. All contents © MuleSoft Inc. API Design
  66. 66. All contents © MuleSoft Inc. Question 1 RESTful API Modeling Language is a human readable language derived based on what data serialization language? a.) Java b.) YAML c.) Spanish d.) Klingon
  67. 67. All contents © MuleSoft Inc. API Fragments • An API fragment is a RAML document that has a version and an identifier, but is not in itself a complete RAML specification • It can be in the form of the following: – Trait – Resource Type – Type – Example – User Documentation – Library – Annotation Type – Security Scheme
  68. 68. All contents © MuleSoft Inc. API Fragments • It’s a key part of API development because it can help you isolate design flaws or problems before you write a line of code. • Instead of starting every project from scratch, you can reuse fragments and APIs to accelerate project delivery.
  69. 69. All contents © MuleSoft Inc. Question 2 What do you call a RAML document that has a version and an identifier, but is not a complete RAML specification? a.) Traits b.) Fragments c.) Shrapnel d.) Debris
  70. 70. All contents © MuleSoft Inc. API Versioning • Versioning is a process of naming and distinguishing between a series of draft documents which lead to a final (or approved) version, which in turn may be subject to further amendments. • Most of the APIs need to release new versions to provide new capabilities and intent. • is important for documents that undergo a lot of revision and redrafting and is particularly important for electronic documents because they can easily be changed by a number of different users.
  71. 71. All contents © MuleSoft Inc. Benefits of API Versioning • Traceability – Being able to see clearly how the project has evolved in the past, and how it is currently evolving, gives project managers the tools they need to steer it in the right direction. • Assurance – Develop Fearlessly • Backup – Not all updates are good updates
  72. 72. All contents © MuleSoft Inc. Question 3 What is the process of creating and managing multiple releases of an API? a.) Caring b.) Loving c.) Versioning d.) Managing
  73. 73. Questions?
  74. 74. Thank you
  75. 75. All contents © MuleSoft Inc. References • Lego Picture – https://medium.com/@thiagonascimento/building-business-like- lego-blocks-api-economy-4cae843cba33 • Document Picture – https://www.iol.co.za/mercury/network/easy-ways-to-scan-and- share-documents-in-seconds-15829883 • Time is money Picture – https://www.projectsmart.co.uk/controlling-project-costs- through-interactive-planning.php
  76. 76. Picture Time
  77. 77. All contents © MuleSoft Inc. Picture Time 77
  78. 78. What’s Next
  79. 79. All contents © MuleSoft Inc. What’s next 79
  80. 80. All contents © MuleSoft Inc. What’s next 80 • Are you ready to step up and share your knowledge? Be the next MuleSoft Meetup Speakers. Feel free to approach the organizers for more information.
  81. 81. All contents © MuleSoft Inc. What’s next 81 • Our next meetup: – Date: April 2019 – Topic: TBD
  82. 82. All contents © MuleSoft Inc. What’s next 82 Share: • Invite your network to join: https://meetups.mulesoft.com/manila/
  83. 83. All contents © MuleSoft Inc. What’s next 83 • Feedback: – Contact your organizers Janos Geronimo, Christopher Co and Ryan Anthony Andal to suggest topics – Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
  84. 84. All contents © MuleSoft Inc. Meetup Survey 84 • Kindly answer: – https://www.surveymonkey.com/r/YDQT99H
  85. 85. Networking time Introduce yourself to your neighbors!
  86. 86. All contents © MuleSoft Inc. Networking time 86 Charades Game Mechanics: • 2 Teams consisting of 4 members (from different companies) • For each team, 1 person will act and the other members will be the ones to guess • No speaking or making sound effects. Only gestures will be allowed • Each team has a maximum of 2 mins to guess the words. • Fastest team to guess the most number of words under 2 mins wins • Guess words are part of the meet up topic
  87. 87. See you next time Please send topic suggestions to the organizer

×