book

RESTful Rails Development

by Silvia Puglisi

October 2015

Intermediate to advanced

350 pages

7h 26m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Why Rails and Not Node.jsWhy (I Think) You Should Read This BookWhat You Will Find in This BookWhat You Will Not Find in This Book (And Where You Can Go for Answers)ResourcesCoding StyleConventions Used in This BookUsing Code ExamplesHow to Contact UsAcknowledgments
REST and HTTPArchitectural AbstractionsIntroducing RESTRESTful Programming and HypermediaDesign ConceptsRESTful ArchitecturesRESTful Interfaces: Hypermedia and Action ControlsWrapping Up
Getting to Know Ruby on RailsSetting Up Ruby and RailsRVMrbenvUsing an InstallerThe Architecture of a Rails AppModel-View-ControllerObject-Relational MappingBundlerChoosing an EditorHello RailsTest-Driven DevelopmentWrapping Up
Application Programming InterfacesDos of API DevelopmentDo KISS and DRYDo URI DesignWhy You Should Use Rails to Build APIsThe WikiCat APIPreparing the DatabaseScaffolding the ModelsCoding Controllers and SerializersTestingWrapping Up
Life Is CRUDRESTful RailsTesting RESTful Routing in RailsHTTP SemanticsGETHEADPOSTPUTDELETEWrapping Up
Hypermedia and Adaptable APIsREST PatternsCreating Hypermedia InterfacesResource-Oriented ThinkingDesigning Explorable ResourcesHATEOASThe WikiCat Hypermedia APIWrapping Up
Asynchronous RESTful OperationsAsynchronous REST in RailsRails Workers and Background JobsCreating an Application Skeleton in Three Easy StepsUploading Images Through an API CallCreating Workers and a Jobs QueueCreating a Resource QueueCallbacksWebSocketsWrapping Up
Testing in RailsMocks, Stubs, Doubles, and DummiesTesting RESTful ServicesWrapping Up
Basics of SOA and Distributed Systems DesignLegaciesHeterogeneityComplexityRedundancyMicroservices ParadigmsThe Evolutionary ApproachThinking in Terms of Microapplications and ServicesThe Thematic Walks APIThe Wikipin APIThe Citywalks APIDiscovering the /lib DirectoryDefining the ModelsBuilding the ControllersWrapping Up
Wanderings in Frontend LandRendering and Templating in RailsEmber.js: A Framework for Creating Ambitious Web ApplicationsDesigned for Application DevelopmentMVC Paradigm of FrontendRails MVC Versus Ember.js MVCPlanning the ApplicationGetting Started with Ember.jsModeling DataRouting in Ember.jsDefining the TemplatesWriting a ComponentExploring Walks Through CategoriesWrapping Up

How Is an API Deployed?API ManagementPaaS SolutionsDeploying the Wikipin API on OpenShiftPreliminary StepsMeet JenkinsWrapping Up
API ManagementAPIs Are Not Consumer ProductsManaging Your Community’s HappinessDeveloper ProgramsApp and API QualityUser HappinessData Management and AnalyticsWrapping Up
Creating a Weather ServiceIf This Then SomethingAdhering to the Terms of ServiceAsynchronous RESTWrapping Up
Web Development Is a Broad TermDeveloping for MobileStreaming Data into a Firefox OS AppDeveloping an Internet of Things AppRails on the Raspberry PiCreating the Raspboard AppWrapping Up
Data Comes from EverywhereMonolithic Versus Microapplication ArchitecturesMonitor, Optimize, and EnhanceApplication LogsMonitor Request Response TimesMonitor ProcessesMonitor Your Server DiagnosticsComprehensive Monitoring SolutionsActions and EventsPlotting DataWrapping Up
Scaling RailsCreating a Middleware for Different APIs to CommunicateConfiguring a Reverse Proxy with NginxMeet LuaBundle Things TogetherCachingScaling Is Not Necessarily Difficult and PainfulWrapping Up
How to Protect User Privacyk-anonymityDifferential PrivacyPrivacy-Enhancing TechnologiesIs My Data Safe?Common Sources of InsecurityIs Rails Secure?SessionsCross-Site Request ForgeryRedirectionFile UploadFile DownloadLogsConclusions
Everything Started with HypertextCreating an HTTP Server in Ruby, QuicklyThe HTTP ProtocolArchitectureParametersMessagesConnectionsStatus Code DefinitionsAccess AuthenticationContent NegotiationCachingSecurity Considerations

Content preview from RESTful Rails Development

Chapter 10. Deploying an API

In this chapter we are going to see what options we have when it comes to deploying our API. Do we need an API management service? What services do we need to be provisioned and managed by third parties, and what can we develop in house? We will see how to deploy one of our APIs to OpenShift, a PaaS solution that can be used to deploy and host applications in the public cloud if you are not ready to invest in infrastructure. We will also familiarize ourselves with concepts like reverse proxies and we will practice with technologies like Ngnix.

How Is an API Deployed?

A RESTful API ultimately lives on the Web, or on a communication network where different parties can expose and consume data streams.

There are different aspects that need to be considered when deploying on the public cloud. For example, would an API management solution help you deploy your API? Or should you consider deploying with infrastructure developed and maintained in house? Which services are you ready to maintain yourself, and which would you like to have provisioned and managed by some third-party service?

There isn’t a general rule of thumb on how to decide which services you’d like to have managed externally and which you’d like to manage and develop in house. Generally speaking, everything that you develop yourself will go through the same design and development stages that your main product has gone through. So, the real question here is: do we have the resources and time ...