Serverless guide #45
Merged
Serverless guide #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
irinanazarova
approved these changes
Nov 3, 2023
docs/README.md
Outdated
|
|
||
| Save up to 10x on infrastructure compared to built-in Action Cable without sacrificing Rails productivity by switching to third-party services: a fast Golang server handles the load, a gRPC-driven Rails application deals with business-logic. The [Pro version](./pro.md) offers even more benefits: an additional 40% reduced memory footprint, DX improvements, and priority support. | ||
| Save up on infrastructure and PaaS bills without sacrificing productivity: a fast Go server handles the load, and your application deals with business logic. The [Pro version](./pro.md) offers even more benefits: an additional 40% reduced memory footprint, DX improvements, and priority support. |
There was a problem hiding this comment.
Let's update the Pro benefits:
The Pro version offers even more benefits: delivery guarantees in cluster mode, fallback transport for private networks, GraphQL integration, added memory efficiency and more.
| @@ -0,0 +1,201 @@ | |||
| # Using AnyCable to power serverless Node.js applications | |||
|
|
|||
| AnyCable is a great companion for your serverless Node.js applications needing real-time features. It can be used as a real-time server with no strings attached: no vendor lock-in, no microservices spaghetti, no unexpected PaaS bills. Keep your logic in one place (your JS application) and let AnyCable handle the low-level stuff. | |||
docs/guides/serverless.md
Outdated
| <img align="center" alt="AnyCable + Node.js serverless architecture" style="max-width:80%" title="AnyCable + Node.js serverless architecture" src="/assets/serverless-light.png"> | ||
| </picture> | ||
|
|
||
| AnyCable-Go will handle WebSocket connections and translate incoming commands into API calls to your serverless functions, where you can manage subscriptions and respond to commands. The client-server communication is expected to use [Action Cable protocol](../misc/action_cable_protocol.md). |
There was a problem hiding this comment.
I would probably remove "The client-server communication is expected to use Action Cable protocol." because it is sort of excessive knowledge, it seems.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview: https://deploy-preview-45--priceless-northcutt-ea746a.netlify.app/edge/guides/serverless
Changes:
/guides/serverlesspage