Announcement

Collapse
No announcement yet.

Scale-out of the vBulletin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Scale-out of the vBulletin

    Please reply about the following.

    Assuming scale-out when using vBulletin on an instance of a cloud server, can it be built in?
    The DB is assumed to be an independent instance, running persistently.

    Thank you.

  • #2
    Your question isn't specific enough to answer. It comes down to a number of things including available hardware and virtualization used in said cloud server. As a generic cloud server, you should be able to add resources as needed to account for demand and remove those resources when the demand subsides.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

    Comment


    • #3
      Thank you and sorry,,

      We are under building a system using vBulletin on AWS and have a question.
      If you run a scalable vBulletin app on an ECS Fargate cluster, is there any consideration other than using persistent DB service like RDS?

      Comment


      • #4
        vBulletin is a PHP/MySQL application. PHP and MySQL have to be accessible to the web server. Once you meet the minimum requirements for vBulletin, how you configure your server is dependent on your server administrators. 95% of our customers run the software on shared hosting services with either cPanel or Plesk. vBulletin will probably run on a Raspberry Pi and be able to support a large number of customers. We previously ran vBulletin Cloud on AWS. Unfortunately, I don't know the specifics on how they configured AWS and we have since brought vBulletin Cloud in house at our own datacenter. Managing AWS simply became too onerous a task for the IT guys when we already have a dedicated datacenter for other corporate services.

        For ECS, your container(s) has to have a web server and PHP running. While we recommend Apache, the web server is your choice. We provide basic rewrites for Apache, NGINX, and IIS. Your RDS must be MySQL or one of its drop in replacement clones.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API

        Comment


        • #5
          Thank you for your advice, but our main concern is the scalability of vBulletin running in ECS containers.
          More specifically, when DB data is persistently kept in RDS for MySQL, supposing containers in which the vBulletin app is embedded are dynamically generated in ECS. At that time is the service be able to run continuously?

          Comment


          • #6
            Your question is really beyond the scope of vBulletin support. vBulletin is not a daemon. It doesn't "run" on the server and has no direct executables. It is a PHP Web App that runs under a web server. It does not maintain state except from data stored in the MySQL database. Each page load can be a separate thread that ends as soon as the page is sent to the browser or the threads can be pooled using technology like FastCGI. If a request is made and your web server doesn't supply a response from PHP and MySQL then the request fails. If this requires that you run persistent instances, then that is the case.
            Translations provided by Google.

            Wayne Luke
            The Rabid Badger - a vBulletin Cloud demonstration site.
            vBulletin 5 API

            Comment


            • #7
              Thank you for your answer.

              Comment

              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
              Working...
              X