CODEWITHSUNDEEP
.netamazon-web-servicesasp.net-coreaws-lambdaaws-api-gateway
Sahil Sharma
Sahil Sharma

Reputation: 4247

Amazon API Gateway for .NET core vs implementing own API gateway?

We are planning to create our own API gateway that will have:

  1. Microservice discovery mechanism
  2. Handling parallel requests
  3. Taking care of authorization

We have most of our APIs already written in .NET 4.5 (nearly 1000 APIs) and I recently read here that we can use Amazon API gateway with .NET core.

I am now wondering if it makes sense to rediscover the wheel when Amazon is already offering similar service? What could be pros and cons of using Amazon API gateway vs creating own API gateway?

Upvotes: 1

Views: 805

Answers (1)

E.J. Brennan
E.J. Brennan

Reputation: 46879

IMO no, it doesn't make any sense to re-create what you can buy for a few pennies, from a team of people who are probably smarter than you (and me) and are constantly improving and monitoring what they have provided.

If the API gateway does what you want, you'd be crazy to write your own - your solution is unlikely to be better, it will almost certainly cost more, and sooner or later you will get tired of supporting it yourself.

Upvotes: 2

Related Questions