Wednesday, May 1, 2019

Structure of web service to integrate two REST APIs

I am writing a program that will be used to pull data from two separate SaaS softwares via their REST APIs - concatenate them, and save the output as raw JSON. When this is complete - the program will be scheduled to run every night.

The overall concept isn't really complicated, it follows a very simple process:

  1. Pull data from Software A via REST
  2. Pull data from Software B via REST
  3. Concatenate them
  4. Save output as raw JSON

I started off by trying to develop this as a .NET Core Console Application. Mostly straightforward - just using appropriate libraries to send/receive HTTP requests to both software APIs, pulling data, and using IO library to save to JSON file.

However - I've been told that this actually needs to be a web service, not a console application. I have basic experience and knowledge regarding web services, but I need some help understanding how to lay out the entire solution from a high-level.

I think I'm getting confused at understanding how exactly web services work and how my original solution would fit into a web service? And how would my final solution be "deployed" and scheduled to run?

How would I structure the 4 step process above if I were to convert my console application to a web service?

Structure of web service to integrate two REST APIs Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team