Timeline for Shared database vs tightly coupled message model
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2020 at 13:03 | vote | accept | johnknoop | ||
| May 4, 2015 at 14:45 | comment | added | cdosborn | Without knowing the details of your application, I would extend webapp with public api to hit the same functions as your service. Then make the main webapp query the api. | |
| May 4, 2015 at 11:26 | comment | added | johnknoop | @cdosborn Agree. But what would be the best way to achieve this? I'm not overly crazy about building a new API inside the web app only to server the public API. I would rather turn it the other way around, and have the webapp call the public API to prevent code repitition. But I'm not completely sold on that either. I'm sure there must be a better way to do this. | |
| May 4, 2015 at 9:31 | history | edited | johnknoop | CC BY-SA 3.0 |
added 342 characters in body
|
| May 4, 2015 at 3:33 | comment | added | cdosborn | The public api is interacting with your service (webapp), so the pub. api should point to your service, not the db which is behind the service. | |
| May 3, 2015 at 21:16 | answer | added | Clément Prévost | timeline score: 1 | |
| May 3, 2015 at 20:34 | history | edited | johnknoop | CC BY-SA 3.0 |
deleted 1 character in body
|
| May 3, 2015 at 19:12 | review | First posts | |||
| May 3, 2015 at 19:32 | |||||
| May 3, 2015 at 19:10 | history | asked | johnknoop | CC BY-SA 3.0 |