Register
Results 1 to 8 of 8
  1. #1
    Kathroman's Avatar
    Posts
    5,452
    Reputation
    286
    Blog Entries
    20
    Tagged in
    2157 Posts
    Add to this user's reputation

    WoW-GPS Pricing API

    Well, I've finally finished the first pass of the first part of the new, open source WoW-GPS.

    I've just spent most of my morning blasting through the README, so I'm not going to go into too much detail here. You can view the source here: https://github.com/camerontweedle/wow-gps-api-pricing

    NOTE: The intended end-user for this part of the project is NOT your average user. This is meant to be used by devs/server admins who would like to run their own, custom pricing API server, either publicly, privately, or locally. As such, it might be a bit too technical for most people, and if you're not familiar with a lot of the prerequisite technology, you'll probably have difficulty getting it up and running. So, if you go and visit that link and have absolutely no idea what's going on, that's ok - this part of the project probably isn't for you.

    If you run into technical issues/bugs, please open an issue on Github. If you just have general questions, or would like some more information about what's going on here, feel free to post in this thread.

    My ultimate goal is that all realms' historical auction data would end up being served by this application running on a public webserver. The 2 best ways for this to happen would be:

    a) Developer(s)/server admin(s) with available server space and time to setup/maintain the application for all or some realms, publicly
    b) Server admin(s) with server space but without skills/resources to setup/maintain the application getting in touch with me to see if we can work something out

    On a philosophical level, one of the nice things about the pricing API is that there really isn't anything about it it that is WoW-GPS-specific, so ultimately, this application could technically be used in order to provide auction pricing information to ANY application/spreadsheet, etc. I really tried to ensure it stands on its own, so if you're interested in using this API for your own project, etc. feel free to give me a shout and I can walk you through some of the implementation details.

    Here's hoping the other 2 parts of the project aren't TOO far behind

    -Kathroman
    Like what you see? Become an Ethereal Contributor to help support the site and gain access to additional perks.

        

    Guides: Thunder Bluff Vendor Supply Route | Entry Level JC Strategy | Alternative DMF Guide

    TSM 2.0: TSM 2.0 Groups & Operations GUIDE | TSM 2.0 Basic JC Shuffler | TSM 2.0 ADVANCED JC Shuffler

  2. #2
    tedj's Avatar
    Posts
    483
    Reputation
    35
    Blog Entries
    2
    Tagged in
    217 Posts
    Add to this user's reputation
    Is there any reason why you chose Ruby and MySQL? Asking because for writing data, NoSQL databases like MongoDB are usually faster at writing huge data loads and, for example, NodeJS is significantly faster than Ruby on Rails.

    Ruby is amazing for scalability and for large teams since it's opinionated (meaning structures are usually pre-defined and everybody will understand your architecture and business logic) whilst NodeJS is more of a "open sandbox" environment. However, NodeJS has been shown to be significantly faster than Ruby. This could potentially improve the data fetches and updates.
    Profession Kits - An Adventure to Millions
    Help and be helped, and we'll have a community.

  3. #3
    Kathroman's Avatar
    Posts
    5,452
    Reputation
    286
    Blog Entries
    20
    Tagged in
    2157 Posts
    Add to this user's reputation
    Quote Originally Posted by tedj View Post
    Is there any reason why you chose Ruby and MySQL? Asking because for writing data, NoSQL databases like MongoDB are usually faster at writing huge data loads and, for example, NodeJS is significantly faster than Ruby on Rails.

    Ruby is amazing for scalability and for large teams since it's opinionated (meaning structures are usually pre-defined and everybody will understand your architecture and business logic) whilst NodeJS is more of a "open sandbox" environment. However, NodeJS has been shown to be significantly faster than Ruby. This could potentially improve the data fetches and updates.
    1) I'm not at all familiar with NodeJS - I thought about starting to learn it a few years back, but based on the state it's in ATM, I'm a bit glad I didn't
    2) I'm not using MySQL, I'm using PostgreSQL, but I doubt it would make a difference. Also, I've opted out of Rails' built-in ORM syntax in this case and instead am using large, single-statement, DB-optimized INSERT/UPDATE code. I was able to increase write performance by 10-15x using this method, so I'm actually not all that concerned about it at this stage.

    Tl;DR - the speed of the app appears to be quite reasonable, at this stage, unless someone has some evidence to the contrary
    Like what you see? Become an Ethereal Contributor to help support the site and gain access to additional perks.

        

    Guides: Thunder Bluff Vendor Supply Route | Entry Level JC Strategy | Alternative DMF Guide

    TSM 2.0: TSM 2.0 Groups & Operations GUIDE | TSM 2.0 Basic JC Shuffler | TSM 2.0 ADVANCED JC Shuffler

  4. #4
    tedj's Avatar
    Posts
    483
    Reputation
    35
    Blog Entries
    2
    Tagged in
    217 Posts
    Add to this user's reputation
    I wasn't saying it's not fast or that it wasn't fast enough Kathroman. I was just asking because I know that, on average, it is, and I was curious if there was any reason why you chose Ruby (I guess I know now).

    Once again, curiosity only - What do you think NodeJS's state is currently bad? (I interpreted this from saying you're glad you didn't go with it)
    Profession Kits - An Adventure to Millions
    Help and be helped, and we'll have a community.

  5. #5