Rust is often seen as just a systems programming language, but it’s actually a versatile general-purpose language. Projects like Tauri (for desktop apps), Leptos (for frontend development), and Axum (for backend development) show that Rust can be used for much more than just systems programming.
When I started learning Rust, I built a web application to practice. Since I’m primarily a backend engineer, this was the area I was most familiar with. I quickly realized that Rust is a great fit for web development. Its features give me confidence in building reliable applications. Let me explain why Rust is perfect for web programming.
The talk is all about it. If you prefer the written form you can check out this article.
Building a cloud service is easier than you might think. The talk covers how to build one.
Lately, it seems like everyone either wants to be an architect or already claims the title. This trend spans multiple domains. For instance, in the world of data, a data architect obsesses over governance and data lineage. Then there’s the Customer Success Architect, tasked with ensuring that clients meet their objectives using a company’s products or services.
In the realm of software, a software architect determines the requirements necessary for building an application and devises the best strategies for implementation. Got a system that’s heavy on reading data? Toss in a cache. Dealing with a high volume of writes? It might be time to deploy a message broker alongside a NoSQL database like Cassandra.
However, when it comes to putting these architectural plans into action, things can get a bit wild. The journey often begins with the struggles of writing unit tests, wading through the complexity of implemented requirements, and culminates in wrestling with tricky issues like cache invalidation or the notorious dual-write problem.
So, let’s inject some clarity into how we structure our code to make it future-proof. Our goal? To create a system that welcomes new team members with ease, stands the test of time, and fortifies itself against bugs. Ideally, our code should resemble a symphony — a seamless flow where chaos is banished and every component excels at its task, much like the components in the Linux paradigm.
The talk is all about it. If you prefer the written form you can check out this article.