[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNDM0ODM","title","Soon to be Ruby on Rails --API programmer","state","published","contactAuthorMethod","email","aboutText","

Good News! The Thai version of this book is completed. I'm working on the English version now. Expecting it to be completed by April.

If you want to start building your new web application and you picked to completely separate Client side and Server side codes completely. Then it's a high chance that you need to build API regardless of what you picked for your frontend.

I've used Ruby on Rails in my software house since 2011 and personally think that it is more than enough for most of my customers.

Now that Ruby on Rails has this \"--api\" option where you only use Rails to build API. No HTML, CSS, JS rendered from backend (except for emails). I only use this \"--api\" option for newer projects and moved my frontend to use NuxtJS, NextJS or AngularJS.

My life is now much simpler because I can now separate task between frontend and backend. My team work more effectively, and even better unit test.

This book is to show you how to write API on Rails. It's purely based on code and building prototype application.

This book will not cover Unit Test, I think it's better to start with the fun part and continue with the boring part in the next book.

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci80NTM5NA","name","SaKKo Sama",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/65929/medium/me.jpg?1425583489","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author