{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by DoctaFaust:
1/26/2023 9:18:11 AM
30
It’s truly time for an engine upgrade
Despite the title I will not scoff at the fact bungie engineers spent 23 HOURS YESTERDAY working on the backend issues so huge respect to that. I doubt anyone would be okay with a workload that much, let alone almost a whole day straight of work. Massive respect to the engineers for that.
However it’s really time for a new engine, it’s really starting to become apparent how difficult it is to manage destiny on the tiger engine with the amount of problems being present almost every week. Weapons and armor being disabled for weeks at a time, API being down multiple times in a row, error codes, server lag and not having this resolved or beginning to be resolved before Lightfall isn’t good.
It’s making your community frustrated right now and will continue to do so until something is done about it. It’s a lot easier said than done and I don’t know the first thing about implementing a new engine but something needs to be done bungie.
Edit: I’m no dev with a triple a portfolio or an experienced programmer/engineer, I doubt anyone is on this forum (maybe some people)
Even so, it’s very noticeable how the cracks are starting to become much more apparent, we can’t normalize game breaking issues like we’ve seen this year of content, and for the possibility for them to get worse. We’re not devs and we don’t have answers but we’re simply trying to convey to bungie that the foundation of this game needs to be fixed.
-
1 Reply[quote]Speaking from 23 years of professional experience as a systems engineer/SRE, without seeing how things work on the back-end, calling for a new engine is likely mildly premature. If I were to guess, bungie doesn't have (SRE|System Eng|DevOp)s (whatever you wanna call them these days) managing infrastructure and operations. Instead, they likely have developers doing it and traditionally, that's always been a horrible idea, because frankly, they really don't have a great track record for knowing how to run operational infrastructure. Writing a whole new engine is painstaking, takes a long time, and is error prone. Besides, why throw the baby out with the bath water. It's better to fix the bugs and enhance the current engine usually. I'm curious, how have you identified that the engine needs work? From a client side of things, I have never seen any significant issues with the game play. The network suuuuucks! That could likely use some work, but as I said, we have no idea how they're running their servers as far as I'm aware. My guess is that their back-end needs some optimization. I *think* they use AWS for their back end infra (based on region names I've seen). At any rate, my guess is that this is where they need help. If they're using kubernetes, then that could cause some additional question in terms of load balancing, ingresses, etc, in my estimation. A new engine would be like taking a hammer to an ant hill I think. I doubt much good can come of that right now if your goal was to still play d2 as it currently is in form. Also, data migration is extremely difficult to perform flawlessly and almost always runs into problems. I doubt db schemas are perfect (assuming they're used, which I'm guessing they are). Migration isn't impossible, but I almost promise you it would never be done. They'd just start over from scratch minus basic player data and if you start with a new engine, that's likely what you would do...at least I would.[/quote] Not me but it gives a very good explanation on why it's not the engine
