Azure redis cache, is it necessary?











up vote
2
down vote

favorite












Currenty we are running Sitecore 9.0 on Azure Paas. I would like to know which is the purpose of the Azure Redis Cache?



Reading some documentation it seems that it´s to store session properties of users. We are an e-commerce site, but we are using a custom mechanism for the users session, not using the one provided by Sitecore. If we are not using it, is it necessary to have the Redis Cache?



We have looked at redis, it contains a hundred of keys, with not readable content for us. In some blogs I read that the Redis Cache it´s useful decreasing response time in requests peaks. But I´m not sure if it´s useful when we are not using Session mechanism from Sitecore.



Thanks






azure paas redis







share|improve this question




























    up vote
    2
    down vote

    favorite












    Currenty we are running Sitecore 9.0 on Azure Paas. I would like to know which is the purpose of the Azure Redis Cache?



    Reading some documentation it seems that it´s to store session properties of users. We are an e-commerce site, but we are using a custom mechanism for the users session, not using the one provided by Sitecore. If we are not using it, is it necessary to have the Redis Cache?



    We have looked at redis, it contains a hundred of keys, with not readable content for us. In some blogs I read that the Redis Cache it´s useful decreasing response time in requests peaks. But I´m not sure if it´s useful when we are not using Session mechanism from Sitecore.



    Thanks






    azure paas redis







    share|improve this question


























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      Currenty we are running Sitecore 9.0 on Azure Paas. I would like to know which is the purpose of the Azure Redis Cache?



      Reading some documentation it seems that it´s to store session properties of users. We are an e-commerce site, but we are using a custom mechanism for the users session, not using the one provided by Sitecore. If we are not using it, is it necessary to have the Redis Cache?



      We have looked at redis, it contains a hundred of keys, with not readable content for us. In some blogs I read that the Redis Cache it´s useful decreasing response time in requests peaks. But I´m not sure if it´s useful when we are not using Session mechanism from Sitecore.



      Thanks






      azure paas redis







      share|improve this question















      Currenty we are running Sitecore 9.0 on Azure Paas. I would like to know which is the purpose of the Azure Redis Cache?



      Reading some documentation it seems that it´s to store session properties of users. We are an e-commerce site, but we are using a custom mechanism for the users session, not using the one provided by Sitecore. If we are not using it, is it necessary to have the Redis Cache?



      We have looked at redis, it contains a hundred of keys, with not readable content for us. In some blogs I read that the Redis Cache it´s useful decreasing response time in requests peaks. But I´m not sure if it´s useful when we are not using Session mechanism from Sitecore.



      Thanks






      azure paas redis




      azure paas redis






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday









      Tamas Varga Sitecore

      2,5661952




      2,5661952










      asked yesterday









      Marc Cals

      1834




      1834






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          7
          down vote













          Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.



          Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support base functionality in Sitecore XP (Analytics, XDB etc). Even if you are using a custom session provider for other purposes, you will likely still need the Sitecore sessions configured to get full value out of the solution. You can find some more information on how Sitecore manages session data here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/session_state



          Redis is designed as a means for fast, distributed access to a key/value store. If you're digging into the redis instance directly, you're likely to see all of the keys of your current sessions (private and shared) with non-readable values (usually stored as binary vals). These values are usually managed and accessed via the Sitecore Session API abstractions. It's rare you would need to access Redis directly.



          Sitecore 9.0 supports Redis and SQL Server as distributed session providers. So, no, Redis is not required...however a session state provider is required for Sitecore XP. ie. You need Redis OR SQL Server configured. Which you select really depends on your exact situation. If required, details on how to configure the SQL provider as an alternative is documented here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_sql_server_provider






          share|improve this answer





















          • Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
            – Marc Cals
            yesterday






          • 1




            Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
            – GWDT
            yesterday













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "664"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15009%2fazure-redis-cache-is-it-necessary%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          7
          down vote













          Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.



          Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support base functionality in Sitecore XP (Analytics, XDB etc). Even if you are using a custom session provider for other purposes, you will likely still need the Sitecore sessions configured to get full value out of the solution. You can find some more information on how Sitecore manages session data here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/session_state



          Redis is designed as a means for fast, distributed access to a key/value store. If you're digging into the redis instance directly, you're likely to see all of the keys of your current sessions (private and shared) with non-readable values (usually stored as binary vals). These values are usually managed and accessed via the Sitecore Session API abstractions. It's rare you would need to access Redis directly.



          Sitecore 9.0 supports Redis and SQL Server as distributed session providers. So, no, Redis is not required...however a session state provider is required for Sitecore XP. ie. You need Redis OR SQL Server configured. Which you select really depends on your exact situation. If required, details on how to configure the SQL provider as an alternative is documented here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_sql_server_provider






          share|improve this answer





















          • Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
            – Marc Cals
            yesterday






          • 1




            Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
            – GWDT
            yesterday

















          up vote
          7
          down vote













          Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.



          Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support base functionality in Sitecore XP (Analytics, XDB etc). Even if you are using a custom session provider for other purposes, you will likely still need the Sitecore sessions configured to get full value out of the solution. You can find some more information on how Sitecore manages session data here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/session_state



          Redis is designed as a means for fast, distributed access to a key/value store. If you're digging into the redis instance directly, you're likely to see all of the keys of your current sessions (private and shared) with non-readable values (usually stored as binary vals). These values are usually managed and accessed via the Sitecore Session API abstractions. It's rare you would need to access Redis directly.



          Sitecore 9.0 supports Redis and SQL Server as distributed session providers. So, no, Redis is not required...however a session state provider is required for Sitecore XP. ie. You need Redis OR SQL Server configured. Which you select really depends on your exact situation. If required, details on how to configure the SQL provider as an alternative is documented here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_sql_server_provider






          share|improve this answer





















          • Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
            – Marc Cals
            yesterday






          • 1




            Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
            – GWDT
            yesterday















          up vote
          7
          down vote










          up vote
          7
          down vote









          Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.



          Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support base functionality in Sitecore XP (Analytics, XDB etc). Even if you are using a custom session provider for other purposes, you will likely still need the Sitecore sessions configured to get full value out of the solution. You can find some more information on how Sitecore manages session data here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/session_state



          Redis is designed as a means for fast, distributed access to a key/value store. If you're digging into the redis instance directly, you're likely to see all of the keys of your current sessions (private and shared) with non-readable values (usually stored as binary vals). These values are usually managed and accessed via the Sitecore Session API abstractions. It's rare you would need to access Redis directly.



          Sitecore 9.0 supports Redis and SQL Server as distributed session providers. So, no, Redis is not required...however a session state provider is required for Sitecore XP. ie. You need Redis OR SQL Server configured. Which you select really depends on your exact situation. If required, details on how to configure the SQL provider as an alternative is documented here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_sql_server_provider






          share|improve this answer












          Azure Redis cache is the default session provider Sitecore 9.0 will use in Azure Paas. Out of the box, Azure Redis Cache will be configured and used by Sitecore.



          Sitecore uses this session provider as a means of managing out of process (ie. distributed) session state to share contact data across browser sessions and devices. This is required to support base functionality in Sitecore XP (Analytics, XDB etc). Even if you are using a custom session provider for other purposes, you will likely still need the Sitecore sessions configured to get full value out of the solution. You can find some more information on how Sitecore manages session data here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/session_state



          Redis is designed as a means for fast, distributed access to a key/value store. If you're digging into the redis instance directly, you're likely to see all of the keys of your current sessions (private and shared) with non-readable values (usually stored as binary vals). These values are usually managed and accessed via the Sitecore Session API abstractions. It's rare you would need to access Redis directly.



          Sitecore 9.0 supports Redis and SQL Server as distributed session providers. So, no, Redis is not required...however a session state provider is required for Sitecore XP. ie. You need Redis OR SQL Server configured. Which you select really depends on your exact situation. If required, details on how to configure the SQL provider as an alternative is documented here:
          https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/session_state/session_state/walkthrough_configuring_a_private_session_state_database_using_the_sql_server_provider







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered yesterday









          GWDT

          815




          815












          • Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
            – Marc Cals
            yesterday






          • 1




            Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
            – GWDT
            yesterday




















          • Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
            – Marc Cals
            yesterday






          • 1




            Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
            – GWDT
            yesterday


















          Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
          – Marc Cals
          yesterday




          Thanks @GWDT for your answer. If we don´t use Services like Analytics, XDB. Is it still recommended to have the session mechanism of Sitecore enabled?
          – Marc Cals
          yesterday




          1




          1




          Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
          – GWDT
          yesterday






          Yes. Sessions are still recommended even using the XM (No analytics or marketing features) topologies. You can find out more on the 9.0 arch options here: doc.sitecore.net/sitecore_experience_platform/…
          – GWDT
          yesterday




















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15009%2fazure-redis-cache-is-it-necessary%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

          Image
          28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
          Read more

          ts Property 'filter' does not exist on type '{}'

          Image
          1 I'm trying to follow Angular Material guide to create a custom filter for autocomplete input text https://material.angular.io/components/autocomplete/overview This is what I have TS import { Component, OnInit } from '@angular/core'; import { TemplateRef } from '@angular/core'; import { FormControl } from "@angular/forms"; import { Observable } from "rxjs"; import { map, startWith, filter } from 'rxjs/operators'; (...) export class AppComponent implements OnInit { title = 'Your Profile'; displayedColumns: string = ['selected', 'name', 'description', 'pnr']; dataSource = ELEMENT_DATA; myControl = new FormControl(); options: any = ['One', 'Two', 'Three']; filteredOptions:
          Read more

          mat-slide-toggle shouldn't change it's state when I click cancel in confirmation window

          Image
          1 When I checked the slide toggle it should work as expected. But when I try to uncheck it there is a confirmation window asking if you are sure. When I click cancel in that confirmation window, still the toggle changes to unchecked, which shouldn't happen. It should stay in the same state. Here is my Html and TS Code // html <mat-slide-toggle (change)="change($event)" [checked]="isChecked()" > To-pay </mat-slide-toggle> TS code: // ts change(e) { if(this.checked) { if(confirm("Are you sure")) { console.log("toggle") } else { e.stopPropagation(); console.log("toggle should not change if I click the cancel button") }
          Read more