A Rubyists Guide to Building an API Layer

Transcript

1. A Rubyists Guide to Building an API Layer Darby Frey Director of Platform Engineering - Belly
5. Digital Customer Loyalty Program
6. Merchant
7. Device Management
8. Mobile
9. Campaigns
10. Auto-Engage
11. Bites
12. Internal Tools
13. Backend Stack
14. Backend Stack
15. Backend Stack
16. Backend Stack • A Simple Framework for Building Microservices • Grape • Roar • ActiveRecord • https://github.com/bellycard/napa
17. How Did We Get Here?
19. Monolith • Scaling problems • Slow to iterate (1+ hour builds, tight coupling) • One API for everything (lots of client concerns)
21. Bellywall • Rails app proxy to SOA - SOA scales better • Authentication and Authorization layer (removed some complexity) • Nearly direct access to services
22. Bellywall • Still a single API • Lots of requests (not mobile friendly) • Clever hacks • Little visibility
24. bellycard.com/api/some_endpoint? expand[]=businesses&expand[] =image&expand[]=reward&expand[] =blurred_image
27. • Confidence • Patterns
30. How Did We Do It?
31. Implementation
32. SpikeArrest VerifyApiKey AssignMessage ExtractVariables RaiseFault ServiceCallout JavaScript Implementation
33. Implementation
34. Implementation
35. Configuration “III. Config - Store config in the environment” http://12factor.net
36. Configuration
37. Configuration
38. DRY
39. DRY
40. Logging
41. Javascript Mashups
42. Can We Make It Easier?
43. Unit / Integration Testing • apigee-mock • Inspired by Sparrow.js • Provides a basic interface to the Apigee JS environment • Allows us to use nock to intercept and stub service requests • https://github.com/darbyfrey/apigee-mock
45. Command Line Tool • apigee_cli • Wraps apigeetool for deployment • Provides a CLI interface to configs and resource files • https://github.com/bellycard/apigee_cli
46. Command Line Tool • Uses .apigeerc for credentials • View and update configuration variables • View, change and remove resource files
47. End To End Testing • clumsy • Uses ngrok • Allows for testing a proxy’s output instead of it’s response • https://github.com/darbyfrey/clumsy
49. End To End Testing 1. Start a test by sending a request to a proxy 2. That request hits the proxy and gets proxied to the ngrok tunnel 3. The ngrok tunnel routes the request back to the same process that initiated the request 4. That process can make assertions based on that inbound request or send back stub data PROXY TEST NGROK
50. How Did It Go?
52. Results • Mobile Teams Love It! • Decreased Turnaround Time • More Confidence • Patterns
53. Thank You Darby Frey @darbyfrey darby@bellycard.com