Timeline for Strategies for Adapting SQL-Based Data Retrieval to a Newly Introduced REST API in a Short Timeline
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2023 at 21:54 | history | edited | J_H | CC BY-SA 4.0 |
nightly backups are important
|
| Sep 22, 2023 at 21:28 | comment | added | JimmyJames | Overall a good answer but I would warn about getting too deep into 'REST' at this point. It means different things to different people. If the team is unfamiliar with using HTTP-based services, that's where I would start. Having a few people on the team who are comfortable with HTTPS/TLS is not going to hurt either. | |
| Sep 22, 2023 at 19:43 | vote | accept | javery | ||
| Sep 22, 2023 at 19:43 | comment | added | javery | We unfortunately don't have any integration tests, no. I work at a small company where our two software engineers write and maintain code for products. I'm a (junior) data analyst that got caught into maintaining (less, but still important) tools we use to run parts of our production process, so I've never written (or seen) integration tests because most of these tools are poorly put together. It is a mess. The worst part is I have no influence on whether they "flip the switch" or not. I agree with you. Thank you for your advice. | |
| Sep 22, 2023 at 19:33 | comment | added | J_H | Yes. And, I don't understand how you could be asking about integration tests. I mean, doesn't the existing codebase already have integration tests, which verify there's N rows or a JOIN produces a certain result? Your existing codebase is unmaintainable if it lacks an adequate test suite. Fix that first, before considering any API interactions. You will definitely need to have some period of overlap where old + new backends are available to your automated tests. Production can have a "flip the switch!" flag day once confidence is built. | |
| Sep 22, 2023 at 19:29 | comment | added | javery | Hi, thanks very much for the detailed answer. Just to clarify -- so, you think I should use the repository pattern to write the adapter layer? Also, how could I do integration tests for the adapter? Are you saying to simply write the integration tests now, and then only use them when the API becomes available? The only problem I see is this (and I should have been more specific in the post, editing now): once the API goes live, access through normal SQL is shut down. Perhaps I could write the tests, so it only grabs data between certain dates? | |
| Sep 22, 2023 at 19:19 | history | edited | J_H | CC BY-SA 4.0 |
added 5 characters in body
|
| Sep 22, 2023 at 19:12 | history | edited | J_H | CC BY-SA 4.0 |
deleted 4 characters in body
|
| Sep 22, 2023 at 19:05 | history | edited | J_H | CC BY-SA 4.0 |
deleted 4 characters in body
|
| Sep 22, 2023 at 19:00 | history | answered | J_H | CC BY-SA 4.0 |