AUAman Upadhyayindev-jedi.hashnode.dev·Sep 28 · 13 min readBackend Architecture: Controllers, Services, Repositories and MiddlewaresWe've talked quite a bit about what happens when a request reaches our backend. We know about HTTP. We know how routing works. We know how data gets serialized and deserialized. We know about authenti00
AUAman Upadhyayindev-jedi.hashnode.dev·Sep 1 · 8 min readValidations and Transformations for Backend EngineersSo far in this series, we've talked about HTTP, routing, serialization, authentication, and how requests eventually reach our backend. But there's one assumption we've quietly been making: The data c00
AUAman Upadhyayindev-jedi.hashnode.dev·Aug 24 · 18 min readAuthentication and Authorization in BackendSo far in this series, we've talked about HTTP, routing, serialization, and how data moves between clients and servers. But eventually, every backend application reaches two very important questions: 00
AUAman Upadhyayindev-jedi.hashnode.dev·Aug 16 · 7 min readSerialization and Deserialization in BackendIn the previous blogs, we've talked about HTTP, requests and responses, and how routing helps a backend decide where an incoming request should go. But there's another interesting question here. Let's00
AUAman Upadhyayindev-jedi.hashnode.dev·Aug 7 · 10 min readRouting in BackendIn the previous blogs, we talked about HTTP, how requests and responses work, different HTTP methods, and why we need a backend. Now let's say we have a request coming into our backend: GET /api/jedi/00