Home
1. Why we are using Golang?
- Golang boasts the ability to support extensive multithreading, concurrency, and optimal performance, a necessity when crawling websites of significant size and content volume.
- With its distinct Goroutines and Channels feature, Golang is optimized for high concurrency, setting it apart from its Java and .NET counterparts. (source: https://www.golangprograms.com/go-language/concurrency.html)
- Golang has seen an upsurge in adoption for microservice architecture, as outlined in a recent article from QArea. (source: https://qarea.com/blog/why-you-should-write-your-next-microservice-using-golang)
2. Is this the correct way to implement rules checking?
- In accordance with the guidelines set forth by HTMLHint, this represents the precise manner in which regulations for HTML standards are to be implemented.
3. Are there any other libraries which Microsoft have developed which could replace the current HTMLHint
- To date, we have yet to identify any Microsoft-provided alternatives for conducting static code analysis of HTML.
4. Why we are Firebase?
- The Firebase interface streamlines server operations and internal functions, resulting in a user-friendly experience that is both efficient and time-saving.
- With Firebase handling the bulk of operational tasks, developers are afforded the luxury of dedicating additional time towards app development.
- Firebase offers a rapid means of validating app concepts, allowing for effortless migration to a more robust "enterprise" configuration.
5. CodeAuditor's Architecture Diagram
Figure: CodeAuditor's Architecture Diagram