Timeline for Is this an appropriate architecture, or can improvements be made?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2019 at 19:18 | history | edited | simbo1905 | CC BY-SA 4.0 | added 3 characters in body |
| Dec 2, 2018 at 9:19 | history | edited | simbo1905 | CC BY-SA 4.0 | deleted 149 characters in body |
| Dec 2, 2018 at 9:13 | history | edited | simbo1905 | CC BY-SA 4.0 | added 40 characters in body |
| Dec 2, 2018 at 9:07 | history | edited | simbo1905 | CC BY-SA 4.0 | added 141 characters in body; added 5 characters in body; deleted 40 characters in body |
| Dec 2, 2018 at 8:57 | comment | added | simbo1905 | I would recommend that you read the official Azure patterns documentation. They are very clear and will give you lots of things you can point to in your discussions. For example, the architecture you have been given is based on CQSR. I found the Azure architecture documentation very good and it covers lots of the well-known patterns with sample code and how to deploy them on Azure. They may not be up to date with Kubernete in the sample code, but certainly for recommendation saround database management and logical layout for CQSR they will be very helpful. | |
| Dec 2, 2018 at 8:51 | history | answered | simbo1905 | CC BY-SA 4.0 |