Apollo Server

[H4ad]

Feature request

Inspired apollo-server-integrations/apollo-server-integration-aws-lambda#38.

Is your feature request related to an issue? Please describe.
Added support for Apollo Server as Framework/Handler.

Describe the solution you would like

In theory, we already have support for Apollo Server if we use express as middleware.
But maybe we can do better, the solutions are:

• Add support for Apollo Server as Framework.
• Add support for Apollo Server as Handler, so you don't need to create another Request/Response.

In both ways, I don't exactly know how to deal with cors, maybe I can create a CorsFramework to wrap around any other framework to add cors features.

Are you willing to resolve this issue by submitting a pull request?

• Yes, I have time and I know how to start.
• Yes, I have time, but I don't know how to start. I would need guidance.
• No, I don't have time, although I believe I could do it if I had time...
• No, I don't have time and I wouldn't even know how to start.

[H4ad]

I did a proof of concept using the express implementation inside Apollo Server and I create apollo-server.framework.ts.

If you want to give it a try, just create the apollo-server.framework.ts file with the contents of the above file and use it like:

import { IncomingMessage, ServerResponse } from 'http';
import { ApolloServer } from '@apollo/server';
import { ServerlessAdapter, getCurrentInvoke } from '@h4ad/serverless-adapter';
import { DefaultHandler } from '@h4ad/serverless-adapter/lib/handlers/default';
import { PromiseResolver } from '@h4ad/serverless-adapter/lib/resolvers/promise';
import {
  ApiGatewayV1Adapter,
  ApiGatewayV2Adapter,
} from '@h4ad/serverless-adapter/lib/adapters/aws';
import { ApolloServerFramework } from '@h4ad/serverless-adapter/lib/frameworks/apollo-server/apollo-server';

type CustomContext = {
  request: IncomingMessage;
  response: ServerResponse;
  lambdaEvent: unknown;
  lambdaContext: unknown;
};

const server = new ApolloServer<CustomContext>({
  typeDefs: 'type Query { x: ID }',
  resolvers: { Query: { x: () => 'hi!' } },
});

const framework = new ApolloServerFramework<CustomContext>({
  context: ({ request, response }) => {
    const { event, context } = getCurrentInvoke();

    return Promise.resolve({
      request: request,
      response: response,
      lambdaEvent: event,
      lambdaContext: context,
    });
  },
});

server.startInBackgroundHandlingStartupErrorsByLoggingAndFailingAllRequests();

// this handler add support for API Gateway v1 and v2, to add another event source, just call addAdapter.
export const handler = ServerlessAdapter.new(server)
  .setHandler(new DefaultHandler())
  .setFramework(framework)
  .setResolver(new PromiseResolver())
  .addAdapter(new ApiGatewayV1Adapter())
  .addAdapter(new ApiGatewayV2Adapter())
  .build();

[H4ad]

I still need to figure out how to handle cors.

In theory, if I recommend the user to configure within API Gateway is not a problem, but we also have to add support for other clouds, this is not an option.

[H4ad]

The problem with cors was solved with CorsFramework

[H4ad]

I'll wait until I have more time to work on #62, after I finish that integration I'll see how it works with Apollo.

For those who want to use Apollo and don't want to wait, just copy the code from apollo-server.framework.ts, install the latest version of the library and be happy.

[H4ad]

Once the body parser frameworks have been completed, I will now work on completing the Apollo server integration.

[github-actions]

🎉 This issue has been resolved in version 2.13.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀