<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Why component architecture fails in Micro-services

Posted by Dileepa WIjayanayake on Apr 16, 2019 1:43:12 PM

As many Enterprise organizations implement Micro-services, they either have non-working or satisfactory implementations of Micro services. This is a trend we have seen the last 2 years within our customer base.  What companies are truly looking for is a workflow solution to re-architect their Micro-services architecture/solution. 


Many of our Enterprise customers who implemented Micro-services without FlowWright implemented these based on existing components, or using component architecture.  Component architecture is great for many software designs but not for Micro-services.  With components depending on sub-components and layers, break down of a one component can break the whole Micro-service infrastructure.  This was one of the main reasons why our customers implement FlowWright based Micro-services.

The other main concern was security; in most component based architecture, layered security can cause many protocol issues, specially due to compatibility.  We saw a few customers running into this issue, where the security protocols or the vpn technology protocols blocked certain components from communication.  As said before, component architecture is good but with the right software design.

Another main reason companies are going in this direction is for them to be able to change the Micro-service business logic easily.  With components with built in business logic and being compiled, a change to the business logic or code can take time, it then has to be tested and deployed. 

So, how to you implement Micro-services using FlowWright?  It really only requires 2 things, FlowWright workflow and the FlowWright REST API.  Design your Micro-service using the graphics workflow designer within FlowWright, then simply use the REST API to invoke the Micro-service from any platform.  It's easier done than said.

What does FlowWright provide for Micro-services?

  • Easy to build business logic and components with a workflow definition
  • Easy deployment, workflow definitions are instantiated as workflow instances
  • Layered security, supports SSL, including certificates, but also many authentication protocols
  • Change Micro-service logic with just a drag and drop within the graphical workflow designer

If a Micro-service is represented by a single workflow definition, using sub-workflow Micro-services can be combined to perform multiple services.  Our customers are always pushing the limits of FlowWright. Want to learn more how your company can benefit from Micro-services? Let's Talk!  New Call-to-action

Topics: .net workflow solution, micro services