Closed
Bug 1096552
Opened 10 years ago
Closed 10 years ago
RIP middleware. Long live dataservice.
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
111
People
(Reporter: selenamarie, Assigned: selenamarie)
References
Details
I propose we do away with "middleware" and create "dataservice". Henceforth it shall be used for making data from our various external resources available via a web api. DataserviceApp is :lars' refactoring of the middleware to be configman-ized utility that standardizes an interface to external resources containing interesting data. The next step (possibly also in this bug.. but maybe broken out) in the evolution is to make the dataservice accessible via the Django API (webapp-django/crashstats/api). I am deconstructing the complete patch proposed early last summer and breaking it into easily reviewable chunks.
Comment 1•10 years ago
|
||
Yay for this! Lars had a really promising prototype which I never had a chance to actually take for a spin because I don't think it ever actually worked but it did look very promising. I would like to suggest though that we do not kill the middleware server yet. We have built the webapp models so that we can replace one of them at a time. That should make for a "softer landing". E.g. the "CurrentProducts.get" might do a `from socorro.external.postgresl.something import Something` instead but we leave "SuperSearch.get" to continue to do a HTTP GET to the middleware service.
Assignee | ||
Comment 2•10 years ago
|
||
(In reply to Peter Bengtsson [:peterbe] from comment #1) > Yay for this! Lars had a really promising prototype which I never had a > chance to actually take for a spin because I don't think it ever actually > worked but it did look very promising. :) Thanks! His code is pretty great. I'm making some minor modifications and am already able to start up the new app. > I would like to suggest though that we do not kill the middleware server > yet. We have built the webapp models so that we can replace one of them at a > time. That should make for a "softer landing". *nod* My thinking is that we deploy DataserviceApp and provide them side-by-side for a transition.
Comment 3•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/958b2b033c0ed28c5a4b7ec4e78e950015a23df3 Fixes bug 1096552 create dataservice https://github.com/mozilla/socorro/commit/3ae48b789a020a6d9f95748f5c77605da8c02c92 Fixes bug 1096552 test tweaks to limit changes to just the Bugs class, errata https://github.com/mozilla/socorro/commit/ead5362f967b77b8f2d8aface5428df8e062f177 Merge pull request #2474 from selenamarie/bug1096552-create-dataservice Fixes bug 1096552 create dataservice
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → 111
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → sdeckelmann
You need to log in
before you can comment on or make changes to this bug.
Description
•