You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In-memory caches are vital when you're building real-time applications like games, ad systems, or financial applications. They're also practical when you want a convenient way to store key values without needing a database. That's why we're excited to let you know that Encore now has native support for in-memory caches, using Redis!
Here's what you need to know
The Encore framework now has a native API for working with caches, and as usual, it works the same across Encore cloud, GCP, and AWS. (Azure coming soon!)
Before trying it out, remember to first update using: encore version update
We've also been busy making improvements to Encore Flow:
Cron Jobs are now included in the Encore Flow architecture diagrams, making it dead simple to see which services have Cron Jobs attached.
You can now easily download an image of your system architecture using the little camera icon in the upper right corner of the Encore Flow view.
Local dev dash refresh
It's been a long time coming, but it's finally done: The local dev dash is now using the same styling as the web platform! We've also made a bunch of usability improvements to make it more intuitive and easier to use. We'd love to hear what you think on Slack!
Bugfixes and other improvements
We're always thankful when we get feedback and bug reports from anyone using Encore. Here are some improvements we've made lately, thanks to your input:
We've given the Encore website a big performance boost, so it loads faster and feels snappier!
We've improved the responsiveness and layout of the docs section so it's easier to use side-by-side with your IDE.
We fixed a bug where Flow wouldn't render properly on Firefox.
Thanks to our contributors
We rely on the community to improve Encore, and we're overwhelmed by your support and encouragement.
Thanks to @bogdaaamn, @Minivera, @Willyham, @davidmytton, @melkstam, MaxD for your ideas, bug reports and feedback!
Introducing our new community forums
For a long time, we've had an active Slack group. It's been a great way for everyone to engage in meaningful conversations, and for us quickly provide help when there are questions. Lately, we've noticed that the drawback with Slack is that it makes it hard for new joiners to discover answers to common questions and refer to past conversations.
We'll use this for asynchronous conversations and to build up a knowledge base of community questions and answers.
If you haven't already, sign up and introduce yourself!
We're not going to stop using Slack, rather we're going to focus it on synchronous and time-sensitive conversations.
What's next
In the coming weeks we'll be adding even more flexibility to the Encore framework, with improved support for configuration. We're also working on a big upgrade to infrastructure provisioning, making it more flexible and easier for you to add specific requirements like deploying to existing Kubernetes clusters. - Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In-memory caches are vital when you're building real-time applications like games, ad systems, or financial applications. They're also practical when you want a convenient way to store key values without needing a database. That's why we're excited to let you know that Encore now has native support for in-memory caches, using Redis!
Here's what you need to know
encore version update
Check out the docs to see how the new cache API works.
Upgrades to Encore Flow
We've also been busy making improvements to Encore Flow:
Local dev dash refresh
It's been a long time coming, but it's finally done: The local dev dash is now using the same styling as the web platform! We've also made a bunch of usability improvements to make it more intuitive and easier to use. We'd love to hear what you think on Slack!
Bugfixes and other improvements
We're always thankful when we get feedback and bug reports from anyone using Encore. Here are some improvements we've made lately, thanks to your input:
Thanks to our contributors
We rely on the community to improve Encore, and we're overwhelmed by your support and encouragement.
Thanks to @bogdaaamn, @Minivera, @Willyham, @davidmytton, @melkstam, MaxD for your ideas, bug reports and feedback!
Introducing our new community forums
For a long time, we've had an active Slack group. It's been a great way for everyone to engage in meaningful conversations, and for us quickly provide help when there are questions. Lately, we've noticed that the drawback with Slack is that it makes it hard for new joiners to discover answers to common questions and refer to past conversations.
That's why we've launched a community forum!
We'll use this for asynchronous conversations and to build up a knowledge base of community questions and answers.
We're not going to stop using Slack, rather we're going to focus it on synchronous and time-sensitive conversations.
What's next
In the coming weeks we'll be adding even more flexibility to the Encore framework, with improved support for configuration. We're also working on a big upgrade to infrastructure provisioning, making it more flexible and easier for you to add specific requirements like deploying to existing Kubernetes clusters. - Remember to vote on your favorite feature on the roadmap!
As always, if you have questions or feedback, tell us on Slack.
We're excited to hear your feedback! ❤️
Catch you in the cloud,
André & the Encore team
This discussion was created from the release Introducing Caches: Use Redis as a native code concept in Encore.
Beta Was this translation helpful? Give feedback.
All reactions