Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production Deployment Best Practices Documentation #523

Open
willbakst opened this issue Sep 25, 2024 · 2 comments
Open

Production Deployment Best Practices Documentation #523

willbakst opened this issue Sep 25, 2024 · 2 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@willbakst
Copy link
Contributor

Description

We should include documentation specifically around best practices to deploy apps built using Mirascope to production.

This should cover things like error handling, retries, and more.

For anyone already deploying to production, feedback and input would be much appreciated here!

@willbakst willbakst added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Sep 25, 2024
@joekendal
Copy link

joekendal commented Sep 25, 2024

with aws serverless constructs, we would be looking to have adapters for the stateful and stateless components:

chat history: dynamodb
compute: lambda

@willbakst
Copy link
Contributor Author

You should be able to use lambda to run the calls, and then pull chat history from dynamodb and insert it as a computed field.

The idea is that inside of your call you would pull the chat history from dynamo.

In the upcoming v1.3 release, this will be more clear when using prompt writing methods like messages shorthand.

Does this make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants