Apigee Interview Questions With Answers

I plan to use node.js and Apigee edge to load a few dozen greater companies like FitBit.com. are you able to deal with how smooth this might be?

That is considered one of our middle product functionalities. lots of our customers use our platform to mixture their records with 0.33-celebration API records like this.   There are masses of public materials approximately it, and you can click on right here to view an existing recorded demo of our product. We also can set up a demo for you; you can request one at the demo web page connected above. Or strive it out yourself with our Apigee developer plan by using travelling /about/pricing/apigee-part-pricing-capabilities.

Corporations like DreamFactory.com divulge a relaxation API to carry out CRUD operations the use of car-technology of CRUD capability. Do you now or will you within the destiny provide such functionality?

The addition of node.js enables through building this kind of capability in our platform, the usage of node.js modules in a very bendy manner. We may also don't forget more tooling assist in future.

Can you explain the difference between sharing statistics via APIs versus net offerings?

APIs are indeed “net services” in that they are programmable offerings invoked over the net the use of HTTP. however, a right “API” normally includes a few manner for a developer to find out about the service (through medical doctors, or a few form of developer portal), and a manner for the developer to sign up thru self-carrier, in place of attending meetings and making phone calls.

Similarly, APIs are designed for use at the net, as opposed to on a non-public network, so that they normally encompass a few form of safety mechanism (regularly OAuth), a few mechanisms that restrict the wide variety of API calls a customer is allowed to make, and additional mechanisms to shield in opposition to threats and accumulate analytics at the site visitors.

Could i use Apigee as a sort of center-tier proxy server to forward relaxation API requests to my 1/3-birthday party vendors like Fitbit.com and Fatsecret.com then ahead the responses to my customers at the purchaser tier?

Definitely. many of our customers use our platform to combination their information with 1/3-celebration API records like this.  you may try it out your self with our Apigee Developer plan; sign up here: http://apigee.com/about/plans.

Besides JSON, do you furthermore may aid conventional XML payloads?

Yes. We help XML and JSON both natively. a lot of our rules and different platform capabilities especially manage XML payloads.

Do you do not forget yourselves to be a node.js rest API dev platform like Cloud9.com, or are you positioning yourselves in a few other area? in that case what is the difference?

Our platform is a great one to use if you are either growing a emblem-new API in node.js, or growing an API out of existing components—and we're persevering with to invest in our platform for this use case. alternatively, there are masses of structures available which are optimized for hosting web pages.

For creating a brand new API, using Apigee offers you the advantage of a platform that solves tough issues which might be precise to the API world, including quota enforcement, chance detection, and OAuth help. in addition, we've the ability to acquire precise analytics on the API traffic and gift them in a manner that is “local” to API developers (as opposed to web app analytics, which can be virtually only designed for internet apps).

For growing an API out of existing parts, you can additionally use the extra capabilities of Apigee part that allow you to create a proxy for an current API (both the usage of a graphical UI, by way of enhancing configuration files, or via writing node.js code), apply the policies like we defined above, and accumulate exceptional analytics.

Does OAuth 2.zero have main performance improvements over OAuth 1.0 and does it do a higher activity at protection?

The distinction is not a lot approximately the performance, but in how flexible the framework is. OAuth 2.0 is a standard, extensible manner to create authorization mechanisms, while OAuth 1.zero most effective really supported one factor.

OAuth 1.0 addressed a much smaller subset of these troubles, and simplest supported one token kind (secret keys encrypted the use of an HMAC) and simplest one way to get tokens (internet browser redirect).

OAuth 2.0 normally uses bearer tokens (random values which can be handed through TLS/SSL as an HTTP header), however those may be received in many approaches, together with an internet browser redirect and a username/password check. The spec committee is operating on additional approaches of having tokens, which includes through signed JSON web tokens (JWT).

What will be the ordinary round-trip time involved in creating a GET approach request to FitBit.com using OAuth 1.0 (and either JSON or XML) with both Apigee.com's implementation of the FitBit platform versus FitBit's implementation of Apigee's relaxation API on the dev.fitbit.com discover API's interface? Platform for platform, how lots faster is JSON versus XML? Or is that just any other huge fable about pace improvements of JSON?

The round-trip time relies upon more on internet latency than whatever else. for example, to get from a mobile device to FitBit and back thru a proxy going for walks in Apigee, your API name travels from the tool to Apigee, then to FitBit, then back through Apigee. depending on in which FitBit’s servers are positioned, that can be whatever from 50 to 100 milliseconds slower (a median latency throughout the U.S.) to nearly the identical.

furthermore, the proxy in Apigee can do such things as cache common responses, dispose of unused bits of the response, and integrate a couple of API calls to the FitBit API right into a single API name from the tool. which means that an API strolling on Apigee may be quicker.

As for XML as opposed to JSON, the actual difference is within the ability for a customer app, consisting of a mobile app, to parse the information. Programmers have a much easier time consuming JSON than XML, due to the fact the information model is an awful lot less complicated and equal, or almost equal, to most programming languages. Parsing XML, then again, calls for a group of specialized information.

In a few cases, parsing XML uses more CPU on the purchaser, however it’s not always a massive difference. similarly, XML is “greater verbose,” however when you compress it, XML and JSON come to be being very similar considering that in the long run they commonly include the equal data.

Does this mean i can construct an API on facet using node that could be a prototype (with, for instance, difficult-coded facts) and later enforce it on my returned quit?

Certainly. one of the creative uses of node.js assist in our platform is to mock your API to observe a completely agile model of development. there are numerous node.js modules that can generate mock APIs from exclusive API definitions.

What could I want Volos for an area account? i'd be higher off usbuiltintegrated the 7fd5144c552f19a3546408d3b9cfb251 area rules for every of built-ings, right?

It relies upon. Many builders, built-inintegrated a majority of busbuiltintegrated clients, love our policy version due to ease of use and simplicity for not unusual API platform-related obligations. but there are a fixed of builders who love to code—integrated a language they know or love.

For the ones developers, Volos is a way to leverage Apigee’s API platform, however built-in their personal manner. Volos also built-in builders to keep away from seller lock-integrated, as they could run their node.js app with Volos node modules built-in any other node built-in, although it gained’t be capable of take built-inintegrated of Apigee platform built-ings.

Can node.js be run natively? I might be incorrect, but from my Play/Scala revel in with Trireme/Rhino, it is form of sluggish. regardless of Play 2.3, TypeSafe is adding an choice to run node.js natively. thoughts?

The most effective TypeSafe factor that i've used up to now is their integration with the Scala build device (sbt), which matches fine and is simple to combine, however it exposes Java’s weak spot, that's startup time. In an internet server, including our integration inside Apigee, Trireme is strolling the same code again and again and it is a good deal closer to local node.js overall performance.

With that stated, Trireme is in no way going to be as rapid for terribly CPU-intensive obligations like node.js on V8. however, most of the use cases that we see are not CPU-intensive and might manage hundreds or thousands of API calls in keeping with 2d the usage of Trireme.

Can you stroll us through a actual-world instance of where node.js with Apigee is used?

We’ll proportion use cases from early adopters of node.js capability in our platform. Built an app backend on top of Solr and cloud-statistics assets to be utilized by on line services. Node.js changed into used to programmatically orchestrate exceptional back-cease services to create a consolidated reaction, which then uncovered an API to their partners and internal employees.

Constructed an API logic layer on top of CRM statistics for field personnel and partners. initially, they had been thinking about a one of a kind node.js platform for growing the app good judgment layer uncovered immediately to their employee application, and had been also considering Apigee aspect for publicity layer for the partners. but once they found out they could leave out out on consolidated analytics, revel in a loss of reuse for other internal packages, and be required to maintain two separate structures, then they considered Apigee edge as the consolidated platform for app good judgment and an exposure layer.