Hi,
Recently a customer shared the following scenario with me. They have a DB layer which is comprised solely of stored procedures. They have 2 thin layers written on top of the DB layer:
As a replacement, I developed a POC on Apigee's HostedTarget itself and used that layer for connecting to the DB, massaging the data as well as exposing the API itself.
Is this a recommended practice? Or am I missing some gotchas here?
Eg: I realized somewhere during the POC that I cannot have multiple versions of the HostedTarget co-exist with variations in the base-path (unlike what is possible with standard Apigee api-proxies).
Can't you connect to the backend API layer (2) from the proxy without a hosted target?
I could use Java callouts to fire the SPs on the DB from the apiproxy itself without using a HostedTarget. But for a variety of reasons I prefer not to use Java callouts unless there is a performance issue which I'm trying to solve.I could also use node.js from within the apiproxy, however as that is being deprecated I would rather not go that route.
Hence the queries:
With multiple revision/basepath deployment are you looking at versioning?
Alternatives,
Thanks @Siddharth Barahalikar for the response.
Versioning isn't really my primary use-case. I just wanted to know if there are any other such points that differ between normal api proxies and hosted targets.
Regarding your other points:
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |