Solution design for logging in UI layer

Asked Apr 26 '16 at 18:34

Active Apr 26 '16 at 18:34

Viewed 205 times

I have standard 3 tier (physical) infrastructure architecture -

UI Layer (ASP.NET MVC)
WebServices Layer (WCF Services)
DB Layer (SQL Server).

All the logging should be done in database using Log4net/EnterpriseLib. There is no direct connection possible between the UI tier and DB tier (because of firewall restrictions) . There is no problem in implementing logging in the "Web Services" layer but I would like ideas to implement logging in the UI layer.

Various options -

a) Implement all UI logging calls via webservices (drawback - performance overhead). Would it be recommended to make async webservice calls in this scenario ?

b) Implement all UI logging calls to store in an intermediate queue in the same machine and run a separate process to transfer the logs to the database.

Please suggest.

I would appreciate if anybody can share his/her real life project experience on this scenario.

asked Apr 26 '16 at 18:34

Subhasis

Why not to allow UI to access db directly? – Maksym Strukov May 02 '16 at 12:20
firewall restriction because of security reasons.... – Subhasis May 08 '16 at 16:44
Yeah, what kind of security reasons? don't you trust your own application? Normally UI has access to a database so you must have specific security requirements. – Maksym Strukov May 09 '16 at 14:03

Solution design for logging in UI layer

0 Answers0