Über den Autor
SWIZEC Teller has been programming for the web since the early 2000's. From a server in his bedroom to web scale cloud ecosystems making millions of dollars. The sysadmin part always annoyed him. Too fiddly.nnServerless caught his eye as the perfect answer to "Quick to get started, easy for engineers to use, fit for scale, no fiddling".nnYou can ask him anything on twitter @swizec, or join the newsletter at swizec.com. He writes about web engineering lessons from practice.
Klappentext
Serverless Handbook for frontend engineers is the resource I wish I had jumping into serverless. A guide borne of experience and pain.nnnNo academic bullshit where you're not sure if the author ever used this stuff in production. I have. From baby side-projects to high traffic data processing monsters.nnnAs Google likes to say: serverless architectures, ¿from prototype to production to planet-scalennnHere's what early readers had to say. nnn- Serverless Handbook taught me high-leveled topics. I don't like specific courses with source code (unless it's the exactly thing I want to build) but these chapters helped me to feel like i'm not a total noob anymore. The hand-drawn diagrams and high-leveled deillegalscriptions gave me the feeling that i don't have any critical "knowledge gaps" anymoren- I'm using these skills on some serverless projects in a dayjob. Also very convenient to use with my side projects.n- The code examples! I like that you included a lot of code examples. It sparked my interest in serverless. Since reading the book I've taken a few courses/workshops in serverless but this was the book that started the serverless journey for me. Can't wait to build a micro SaaS app with my friendsnnnServerless Handbook takes you from backend beginner to solid full-stack engineer. It shows you the mindsets and tactics to use with any backend. It talks about distributed data processing, designing a REST API, how to build GraphQL, handling authentication, and keeping your code secure.nnnEvery chapter helps you choose what to do. Because your project is unique and understanding beats cookie-cutter recipes. This book is a why, not a how. But there's enough how to start you off :)nnnServerless Handbook is everything I wish I knew about backend programming 10 years ago.
