Merging Microservice Architecture with SOA Practices - Tuesday, September 16, 2014

  • By Mohamed Usama Mansoor
  • 16 Sep, 2014
Archived Content
This article is provided for historical perspective only, and may not reflect current conditions. Please refer to relevant product page for more up-to-date product information and resources.

Microservice architecture promises to pragmatically overcome service development hurdles by using a single responsibility pattern (SRP) and full-stack development teams. Do we now throw out SOA and integration practices? In this session, Chris Haddad, VP - Platform Evangelism at WSO2, will describe how you can rapidly build systems by adapting SOA practices, extending your DevOps toolchest, and defining microservices. You will learn:

  • How to properly define, decouple, and size a micro service
  • What DevOps practices overcome microservice deployment roadblocks
  • When microservices create fragile instead of anti-fragile building blocks
Chris Haddad Vice President - Platform Evangelism, WSO2 Chris is responsible for raising visibility, awareness, and knowledge of the unique advantages provided by WSO2’s lean, fully componentized, open source middleware for on-premise and in the cloud. He works closely with developers, architects, and C-level executives to increase WSO2 technology adoption, improve the middleware platform, and maximize customer value. He also works with the engineering team to define the product roadmaps for WSO2’s Carbon and Stratos platforms.