APIs and Servers and Whatnot
APIs and Servers and Whatnot
The following 2 books are included in this bundle...
About the Bundle
Your API has to go somewhere, and unless you're literally made of money, and have some way to get that money through Heroku's payment gateway, then you need to know how to manage a server.
About the Books
Build APIs You Won't Hate
Everyone and their dog wants an API, so you should probably learn how to build them.
API development is becoming increasingly common for server-side developers thanks to the rise of front-end JavaScript frameworks, iPhone applications, and API-centric architectures. It might seem like grabbing stuff from a data source and shoving it out as JSON would be easy, but surviving changes in business logic, database schema updates, new features, or deprecated endpoints can be a nightmare.
After finding many of the existing resources for API development to be lacking, Phil learned a lot of things the hard way through years of trial and error. This book aims to condense that experience, taking examples and explanations further than the trivial apples and pears nonsense tutorials often provide.
Phil worked primarily as an API developer for the last three years. One horror was managing an API built in FuelPHP by a freelancer at the million dollar startup he joined. It was utilizing a then deprecated ORM which had been hacked to death by the previous developer, so took the time to delete that mess and build the next version in Laravel, leveraging it's simple routing, database migrations, schema, seeding, etc. When the following major version of the API was built no rewrite was required, and both managed to live side-by-side on the same "API" servers.
By passing on some best practices and general good advice you can hit the ground running with API development, combined with some horror stories and how they were overcome/avoided/averted. This book will discuss the theory of designing and building APIs in any language or framework, with this theory applied in PHP-based examples.
Some of the more advanced topics covered here are endpoint testing, embedding data objects in a consistent and scalable manner, paginating responses (including embedded objects) and hypermedia "HATEOAS" controls.
Servers for Hackers
Server Administration for Programmers
Don't catch Accidental Sysadmin Syndrome™
Application development is getting more complex, and we developers need to know how to setup and maintain the servers that run our applications. Don’t get stuck at 3am with a broken server, or in the middle of your workday fighting configuration. Learn how to administer your servers!
Run & Manage Web Servers
Learn how to install and configure Nginx, Apache so you can serve your web applications.
Multi-Server Setup
Learn how to connect multiple servers so they can work together for load balancing, caching, redundancy and more.
Latest Technologies
Learn how to install and manage the latest technologies, including setting up queues/workers, monitoring processes so they don’t fail, handling server and applications logging and more!
Setup and Security
Learn how to setup each server with needed software and security configuration to keep your applications and their data safe.
This includes preventing unauthorized access, managing permissions and users, learning how to use the iptables firewall, configuring SSH, enabling SSL certificates and more!
Case Studies
Read the case studies to learn from specific examples from real-world usage.
These includes examples of load balancing, web server configuration, caching and more!
About the Authors
Phil has seen a few trends come and go during a long and varied career of building stuff for money as an employee, freelancer, consultant and now CTO. One trend over recent years is the rise of APIs as an everyday part of the average server-side developers job.
Back in 2009 Phil released a CodeIgniter Rest Server, wrote a few articles about how to use it and built handfuls of APIs for his freelance clients. This tool was fairly basic, but covered HTTP-based routing, HTTP Basic/Digest/API Key authentication, added logging and throttling and did not force CRUD-based conventions. The internet seemed to like it, and this code is still used by Apple, the UN and USA.gov.
Later on as a core-contributor to FuelPHP he added this functionality to the core, and again built out a bunch of APIs for people. Then he got a job in NYC, to take over as Lead Engineer for a company that - you guessed it - had a FuelPHP API and wanted to improve it.
After two years of working on their API, Phil has moved to Ride.com, building their API with an amazing team of developers.
Phil has been building APIs for so long, he has come up with a very long list of ways to make them not suck, and he'd like to share the information with you all.
I'm Chris Fidao. I write Servers for Hackers, the newsletter read by over 11000 programmers who want to learn about the servers their applications run on.
I code software at UserScape, write about software at fideloper.com and, of course, write about servers at serversforhackers.com. Find me on twitter @fideloper.
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...
