Apigee is not middleware or Integration replacement

Apigee is the Gateway

Not Middleware or Integration framework nor for replacing such U.C

Understand that Apigee can do the SOAP to REST or REST to SOAP conversion, but is not replacement to ESB or Message Broker, which involves complex transformations for Legacy modernization.

There are other value adds to Gateway, but correct design would be to have the ESB or Message Broker do the Integration and ETL handle the File or Batch process. Apigee is more Async and Realtime.

We understand that On - Premise Apigee can process the max of 10 MB of File enabling the Streaming and without usage of any Policy, which would require processing the Data for Stream enabled Use case.

When it comes to above U.C, scenario I believe we should continue doing such enhancements in ESB/IIB/ETL.

0 4 2,128
4 REPLIES 4

Hi @Abiram Radhakrishnan,

Yes, your understanding is correct. As APIGEE works as a facade for your backend its better to use ESB for backend functionality. APIGEE is more of the sync and realtime. However you can also think of having microservices for your backend which can replace your ESB.

If in case where the system don't have ESB or ETL or any Message broker currently, then end goal should be to have backend expose the REST or SOAP based Services least thro required framework (Like Spring Boot or from old Legacy). Then API Gateway can take remaining part further.

yes, that is right. you could choose the hybrid model also on apigee which is called microgateway.

Another consideration is that the gateway an extension of infrastructure not the app stack. If you used the gateway as a traditional ESB (integration tool) you are tightly coupling the gateway to the application which, in turn, decrease velocity.

IMHO the gateway is managed by a small team of folks who focus on cross cutting concerns like security, logging, monitoring, threat, etc and not orchestration, enrichment and/or conversion. While the gateway can do much of this its the case where just because you can doesn't mean you should.