10 docs tagged with "architecture"

Why Should We Care About Architecture?

An online judge is primarily a place where you can execute code remotely for educational or recruitment purposes. In this design, we focus on designing an OJ for interview preparation like Leetcode.

Very Large JS App = a lot of developers + large codebase. How to deal with a lot of developers? Empathy and good programming model. How to deal with a large codebase? Code Removability/Delete-ability. Be careful with abstractions.

Fraud Detection fights against account takeovers and Botnet attacks during login. Semi-supervised learning has better learning accuracy than unsupervised learning and less time and costs than supervised learning.

Architecture serves the entire lifecycle of software systems, making them easy to understand, develop, test, deploy, and operate, with the goal of minimizing the human resource costs for each business use case. O'Reilly's

Architecture can directly impact costs per feature. Let's compare Tight-coupling MVC, Cocoa MVC, MVP, MVVM, and VIPER in three dimensions: balanced distribution of responsibility among feature actors, testability and ease of use and maintainability.

Using Lambda can address three issues brought by big data: accuracy (good); latency (fast); throughput (high). The lambda architecture can guide us on how to scale a data system.

How can advertising campaigns achieve higher returns with less money and fewer people? Lyft's answer is automation, which includes an LTV prediction module, a budget allocation module, and a delivery module. When people are freed from tedious delivery tasks and can focus on understanding users, channels, and the messages they need to convey to their audience, they can achieve better campaign results.

Why Do We Need Such Frameworks?

Architecture is the shape of the software system. It helps us to focus more on the structure of the system than on its features and functions. The ultimate goal of architecture is to save human resources costs per feature.