Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Dockerizing Mule ESB

1,287 views

Published on

Dockerizing Mule ESB

Published in: Technology
  • Be the first to like this

Dockerizing Mule ESB

  1. 1. Build Ship Run
  2. 2. Challenge
  3. 3. When something goes wrong.. 
  4. 4. Cargo Transport 1960s
  5. 5. Solution: Intermodal Shipping Container
  6. 6. Docker is a Container System for Code
  7. 7. Ok so what does that give us?
  8. 8. Developer: Build Once, Run Anywhere A clean, safe, hygienic and portable runtime environment for your app. No worries about missing dependencies, packages and other pain points during subsequent deployments. Run each app in its own isolated container, so you can run various versions of libraries and other dependencies for each app without worrying Automate testing, integration, packaging…anything you can script Reduce/eliminate concerns about compatibility on different platforms, either your own or your customers.
  9. 9. Operator: Configure Once, Run Anything Make the entire lifecycle more efficient, consistent, and repeatable Increase the quality of code produced by developers. Eliminate inconsistencies between development, test, production, and customer environments Support segregation of duties Significantly improves the speed and reliability of continuous deployment and continuous integration systems Because the containers are so lightweight, address significant performance, costs, deployment, and portability issues normally associated with VMs
  10. 10. Why it works—separation of concerns • Dan the Developer • Worries about what’s “inside” the container • His code • His Libraries • His Package Manager • His Apps • His Data • All Linux servers look the same • Oscarthe Ops Guy • Worries about what’s “outside” the container • Logging • Remote access • Monitoring • Network config • All containers start, stop, copy, attach, migrate, etc. the same way
  11. 11. Containers vs. VMs
  12. 12. People were like….
  13. 13. Dockerfile for MMC Server FROM image:version COPY your_app_code RUN your_cmds_before_app EXPOSE port CMD to_run_app FROM codingtony/java MAINTAINER vallurusateesh2009(at)google(dot)com RUN wget https://repository.mulesoft.org/nexus/content/repositories/releases/org/ mule/distributions/mule-standalone/3.5.0/mule-standalone-3.5.0.tar.gz RUN cd /opt && tar xvzf ~/mule-standalone-3.5.0.tar.gz RUN echo "4a94356f7401ac8be30a992a414ca9b9 /mule-standalone- 3.5.0.tar.gz" | md5sum -c RUN rm ~/mule-standalone-3.5.0.tar.gz RUN ln -s /opt/mule-standalone-3.5.0 /opt/mule CMD [ "/opt/mule/bin/mule" ]
  14. 14. Bored.. Lets code
  15. 15. Partner Eco System
  16. 16. What is Docker Docker is “an open source project to pack, ship and run any application as a lightweight container.” The idea is to provide a comprehensive abstraction layer that allows developers to “containerize” or “package” any application and have it run on any infrastructure Docker containers provide a standard, consistent way of packaging just about any application.
  17. 17. Since it started in March 2013... • >200,000 pulls • >7,500 github stars • >200 significant contributors • >200 projects built on top of docker • UIs, mini-PaaS, Remote Desktop... • 1000’s of Dockerized applications  Memcached, Redis, Node.js, Hadoop... • Integrationin Jenkins, Travis, Chef, Puppet, Vagrantand OpenStack • Meetups arrangedaround the world…  with organizations likeEbay, Cloudflare, Yandex, and Rackspace presenting on their use of Docker

×