Microservices: Death of the Enterprise Service Bus. Speaker: Kai Wähner

แชร์
ฝัง
  • เผยแพร่เมื่อ 12 เม.ย. 2016
  • Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. Continuous Integration and Continuous Delivery control deployments. This way you get shorter time to results and increased flexibility. Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs. This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB).
    jDays 2016.

ความคิดเห็น • 9

  • @sivakanagaraj8894
    @sivakanagaraj8894 5 ปีที่แล้ว +8

    Death of ESB? We tried to convert 1 mainframe application into Micro service. Nothing worked because no one knows intrinsic of the COBOL modules. Why? There are no documents and no SMEs. We ended up going for 3rd party packaged solution and integrated using ESB. Many folks are completely confused between SOA vs Micro services. The later is related to Application architecture and the former is related to integration architecture. I was told in 1998 that Mainframe will be gone in few years. Till date nothing happened, most organizations have replaced the front end blue screens of Mainframe with J2EE but the core functionality remains in Mainframe. The throughput of 100k transactions per second provided by Mainframe can not be replaced by UNIX. What you are saying make sense for customer based fine grain messages, but when it comes to Enterprise application built for business users can not be done using micro services because most of them are carrying coarse grained messages having 100 different attributes. I have seen people writing micro services and finally ending up with another mess of spaghetti monolithic applications. If it is new application, go far cloud based, big data and micro services...but still I don't know how micro services work without a bus when it comes to async messages...

    • @jayak3768
      @jayak3768 ปีที่แล้ว

      You are absolutely right. I have seen this kind of articles so many times. Microservice vs ESB it's like java vs SQL. They solve different problems and are designed for different needs. They are not competing technologies.
      Enterprise application should not expose microservice interface. That micro service interface is for intra application communication and break down or application componentization.

  • @007indrajeet
    @007indrajeet 8 ปีที่แล้ว +1

    That's a wonderful session kai, keep information and your thoughts posted on you tube.

  • @yamigilgtz
    @yamigilgtz 4 ปีที่แล้ว

    This video is great, thanks for sharing your knowledge

  • @maikbanner7552
    @maikbanner7552 5 ปีที่แล้ว

    Hi
    Very well done presentation, thank you for your time.

  • @sujukrish
    @sujukrish 6 ปีที่แล้ว

    Great. Lot on insights

  • @SmasherHell
    @SmasherHell 4 ปีที่แล้ว +1

    Comparing an architecture with a integration solution ? To me the title sounds like carot farming ! The death of soup factory

  • @freshmikey82
    @freshmikey82 6 ปีที่แล้ว

    Death of the Enterprise Service Bus? Definitely not

  • @Jadeglobal
    @Jadeglobal 5 ปีที่แล้ว

    We have successfully helped many clients streamline their business processes through more efficient use of applications, improve their competitive position in the market through seamless integration across applications or creative enhancements and reduce their overall cost with B2B automation or self-service solutions for customers, suppliers and employees.To know more visit www.jadeglobal.com/services/enterprise-application-services/oracle