ESB when to use/not

ESB	SOAP/HTTP	JMS	FTP	FTP No Changes in File
SOAP/HTTP				N/A
JMS				N/A
FTP

 

MOVE IT/ UCF	FTP	FTP Changes in File
FTP

 

	Good to Use
ü  Integrate with more than 2 System/Application
ü  Integration between application/System with different  data format/protocol
ü  More frequent changes/deployment in provider system , Integration should happens through ESB.It prevents the changes/impact in the Consumer
ü  Same Provider Services consumed by different consumer with minimum changes , integration should happens through ESB
ü  Any Data Enrichment required during  the Integration then it will integrate through ESB
ü  Consumer Integrate more than one Application/System based on the Input ie Routing on fly Routing logic should be in ESB not in Consumer
ü  Data Filtering required while doing Integration , Filtering should be in ESB not in Consumer System
ü  Offline Jobs requires the data(not bulk) from any provider system/application , it will go through ESB not P2P.

 

		Try  to Avoid
	ü  Just need the FTP files between the application/systems ü  Just need the FTP files between the application/systems ü  Bulk Data Processing is not advisable approach to do in ESB. ü  Integration between two application/system in adhoc based then stick with P2P instead of ESB to prevent the ESB’s resource usage. ü  Maintains any state between the services/application/systems. ü  Not to use YAGNI(You Aren't Gonna Need !..) or YNNI (You never need it now) ü  Performance is Key ü  Should not use for Data Replication between the DB/application/systems ü  Provider System does not have the Service Capability or data through adaptor and same provider system(s) is in sunset stage then use P2P ü  Triggering the scheduler job not in ESB.