AWS Amplify Console вЂ“ When youвЂ™re ready to deploy the app, you can just connect your GitHub repository.AWS AppSync enables developers to interact with their data by using a managed GraphQL service. AWS AppSync вЂ“ This is the primary way that the app interacts with the backend.The service returns a JWT token after a successful sign-in, and you use this JWT token to identify the user when youвЂ™re making a request to AWS AppSync. Amazon Cognito user pools вЂ“ This allows the application to handle user sign-ups and sign-ins.The Auth module integrates with Amazon Cognito, and the API module integrates with AWS AppSync. You use the following modules: Auth and API. Amplify Framework вЂ“ This allows you to rapidly bootstrap the projectвЂ™s integration with other AWS services.The application uses a number of AWS services: The underlying detail of which protocol (HTTP/HTTPS or WebSocket) is abstracted away from the developer. Instead of defining routes, customers define a schema, the various data sources that they require, and then use Amplify Framework, an opinionated framework, to interact with AWS AppSync. AWS AppSync and Amplify Framework вЂ“ Customer focus shifts even higher up the stack for both frontend and backend. The customer still must define two API Gateways, one for the standard requestвЂ“response model and one for the WebSocket.ДЈ. AWS manages the infrastructure of both the API Gateway and the backend compute that would be running in Lambda. Amazon API Gateway and AWS Lambda вЂ“ Customer focus shifts up the stack and concentrate on implementing the backend that would respond to the routes that are defined at the gateway level.

Amazon EC2 and Elastic Load Balancing вЂ“ The customer is responsible for configuring, patching, maintaining, implementing high availability, and automatically scaling the backend infrastructure.Дў. Some (but not all) of the approaches that customers can use are as follows:ДЎ. With AWS, you can accomplish these in a number of different ways. This is normally accomplished by means of a stateful WebSocket protocol The second type of endpoint enables persistent connectivity and allows the server to push information to the clients. The first type of endpoint typically involves a standard stateless requestвЂ“response type of interaction, which is handled over traditional HTTP/HTTPS protocol. This article was written byВ Jan Michael Go Tan,В Specialist SA at AWSД«uilding real-time applications normally requires two types of endpoints.

Real time web monitor