Navigation

    FusionAuth
    • Login
    • Search
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs

    Does FusionAuth support high availability database configurations?

    Q&A
    database availability faq
    2
    3
    227
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dan
      dan last edited by

      With a primary/secondary and replication, to ensure availability of the user identity management service?

      --
      FusionAuth - Auth for devs, built by devs.
      https://fusionauth.io

      1 Reply Last reply Reply Quote 0
      • dan
        dan last edited by

        Yes. We don't have any specific guidance around using MySQL and PostgreSQL in an high availability configuration. However, it should work. This document discusses the various possible architectures at a high level: https://fusionauth.io/docs/v1/tech/installation-guide/server-layout

        It is worth noting that MySQL group replication will not work. It requires a primary key on each table. We do not meet this requirement and have no plans to adjust the schema for this style of replication to work. Other types of replication that do not require a PK on every table should work.

        The particulars of DB clustering are outside of the scope of what we can assist with, however.

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • K
          kevin.mahoney last edited by

          @dan there's one important case not covered in those docs - a high-availability database configuration with a single write-instance and one (or many) read-instances (or replicas.)

          Does FusionAuth support this? Typically support means that read-only queries are routed to this read-replica by the application, in order to reduce querying load on the primary write instance.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post