Thinking Outside the Container: Deploying Standalone Apps to Cloud Foundry

Thinking Outside the Container:Deploying Standalone Apps to Cloud Foundry

Jennifer Hickey

© 2012 SpringOne 2GX. All rights reserved. Do not distribute without permission.

Saturday, October 20, 2012

About Jennifer• Engineer @ Cloud Foundry• Focused on framework support• Long time SpringSource-er• Contributed to many Spring and SpringSource projects• Passionate about increasing developer productivity in the

cloud.

2

Contact InfoTwitter: @jencompgeekEmail: [email protected]


mailto:[email protected]

mailto:[email protected]

Cloud Foundry Big Picture

3

Clou

d Pr

ovid

er In

terfa

ce

Application Service Interface

Private Clouds

PublicClouds

MicroCloud Foundry

Data Services

Other Services

Msg Services

.js

Apache2 license


4

• Java–Spring–Grails–Lift–Play

• Ruby–Rails–Sinatra–Rack

• Node.js

Core Runtimes and Frameworks


5

• Python–Django–WSGI

• Erlang OTP/Rebar• PHP• Perl• .Net

–On Iron Foundry

Community and partners contributions


6

The Platinum Rule

Treat each framework the way it wants to be treated!


7

• Command-line for application management–Create apps and services–Update bindings, memory etc.–Scale instances

• Access service and app info through environment variables–Service host, port, credentials–App ip and port

• A runtime library–Connect to services–Retrieve app info

Common Framework Support


Common Framework Support• Auto-reconfiguration for typical apps• Access to services through Caldecott

–Creates tunnel for local clients–Mysql, Mongo, Redis CLIs, etc

• Manifest support

8Saturday, October 20, 2012

This Looks Great! But....

My App Doesn’t Use Any of These Frameworks!


Standalone: The “no framework” framework• Cloud Foundry now supports standalone applications!• Choose a runtime and provide a start command

–

10

$ vmc push myappDetected a Standalone Application, is this correct? [Yn]:1: java2: node3: ruby184: ruby19Select Runtime [java]:Start Command: java -jar myapp.jar


Uses of Standalone Applications• Async Web Frameworks• BYOC: Embedding Jetty or Tomcat• Distributed polyglot applications• Workers


Call Me Maybe?• New frameworks are concurrent, asynchronous, event-

driven–C10K–Thread per request/response isn’t going to cut it

• Single thread to handle multiple connections–Callbacks

• Most use Netty for NIO• Some examples

–vert.x, Blue Eyes, Spray, Unfiltered, Finagle


vert.x - Asynchronous, Event-Driven Java


SockJS - WebSocket Emulation• Cloud Foundry does not (yet) support WebSocket• SockJS emulates WebSocket

–Provides low latency, full duplex, cross-domain communication channel between browser and web server

• Available for Node.js and vert.x–Also Erlang, Lua (Luvit), Python (Tornado)


Demo

Vert.x with SockJS on Cloud Foundry




Why BYOC?• Framework programming model

–Unfiltered with Jetty support• Outpace the CF engineers

–Tomcat 7/Servlet 3.0• http://blog.cloudfoundry.org/2012/06/18/deploying-tomcat-7-using-the-standalone-framework/

• Be cutting-edge–Clojure

• http://blog.cloudfoundry.org/2012/09/25/experimental-clojure-support-in-cloud-foundry/


http://blog.cloudfoundry.org/2012/06/18/deploying-tomcat-7-using-the-standalone-framework/




http://blog.cloudfoundry.org/2012/09/25/experimental-clojure-support-in-cloud-foundry/




More reasons to BYOC....• Deploy legacy EJB apps

–TomEE• Customize Tomcat

–Change logging, server config, etc


Demo

Unfiltered with Jetty on Cloud Foundry




WidgetInventoryService

AccountingService

ShippingService

@ControllerStoreFront

GadgetInventoryService

RDBMS

wgrus-monolithic.war


It’s simple to develop but ....• Lack of scalability

–Scale through replication–Non-replicable component => nothing can be replicated–Can’t scale different parts of the application differently

• Lack of deployability–Deploy it all in one go–Increased risk of something breaking


And....• Applications are brittle

–Store can’t accept orders unless all services are available–Failure (e.g. memory leak) in one component can take down

every other • Monolingual

–Can’t use non-JVM server-side technologies: NodeJS, Rails


Modern Applications• Multiple types of clients

–Mobile–HTML 5–Desktop

• Polyglot applications–NodeJS front-end–Java/Scala backend

• Asynchronous–RabbitMQ


And....• Polyglot persistence

–Relational–NoSQL–NewSQL

• Social network integration


Addressing the Scalability Problem


27

The App


Simple Distribution

28

Backend

Frontend

HTTP


Widening Distribution

29

Frontend 1

HTTP

Backend 1



29

Frontend 1

HTTP

Backend 1Backend 2



29

Frontend 1

HTTP

Backend 1Backend 2 Backend 3



29

Frontend 1

HTTP


Frontend 2



29

Frontend 1

HTTP


Frontend 2 Frontend 3


Scaling out in Cloud Foundry

vmc instances <app> 5


Cloud Foundry Manifests

31

---applications: ./frontend: ... depends-on: ./backend ./backend: ...


ShippingService

StoreFront

wgrus-store.war

AccountingService

wgrus-billing.war

wgrus-shipping


wgrus-inventory


MySQL


Demo

Distributed polyglot WGRUS


Scaling out through Akka• Remote actors

–Location transparent and distributable by design–Netty based in Akka 2.0–Needs cluster-like management


Remote Actors and Routing

35

Frontend 2Router

Frontend 1Router

Backend 1

Netty

Backend 2

Netty

173.14.13.3:57895173.136.3.4:59807


Akka: Messaging based remoting

36

Frontend 1



AMQP/Redis


Demo

WGRUS with Akka


Widening Distribution: Messaging Middleware

38

Frontend 1




ShippingService

StoreFront

wgrus-store.war

AccountingService

wgrus-billing

wgrus-shipping


wgrus-inventory


MySQL

39

Message Broker


Spring Integration• High-level of abstraction for building message based

applications• Implements EAI patterns• Provides plumbing for exchanging messages between

application components• Promotes loosely coupled components• Integrates with external messaging infrastructure: JMS,

AMQP, HTTP, Email, File transfer


Spring Integration Concepts• Message channel

–Virtual pipe connecting producer and consumer• Message endpoints

–The filter of a pipes-and-filter architecture–Read from and/or write to channel


Spring Integration Endpoints• Endpoint types

–Transformer–Filter–Router–Splitter–Aggregator–ServiceActivator–Inbound channel adapter - read from external source, writes to

channel–Outbound channel adapter - read from channel write to external

destination42


Demo

WGRUS with Spring Integration




Get to Work!• Update search indexes!• Email your users!• Backup your data!• Upload new data from external storage!


Polling for Tweets with Spring Integration

46

<int-twitter:search-inbound-channel-adapter id="twitter" query="cloud"> <int:poller fixed-rate="5000" max-messages-per-poll="10"/> </int-twitter:search-inbound-channel-adapter>

! <int:transformer input-channel="twitter" expression="payload.fromUser + ': ' + payload.text" output-channel="rabbit"/>

! <int-amqp:outbound-channel-adapter id="rabbit" exchange-name="tweets"/>

! <rabbit:fanout-exchange name="tweets" durable="false"/>! <rabbit:admin connection-factory="rabbitConnectionFactory"/>! <rabbit:template id="amqpTemplate" connection-factory="rabbitConnectionFactory"/>

! <beans profile="default">! ! <rabbit:connection-factory id="rabbitConnectionFactory"/>! </beans>

! <beans profile="cloud">! ! <cloud:rabbit-connection-factory id="rabbitConnectionFactory"/>! </beans>


Batch Processing with Spring Batch


Spring Batch • Supports Batch API...

–Jobs have Steps–Steps have Readers, and optional Processors and Writers

• Readers read data• Processors process data coming into them, optionally transforming it. Optional.

• Writers write data out


Demo

Spring Batch Working it on Cloud Foundry


Practical Tips

Packaging Your App


Maven Appassembler• Creates start script and packages all deps in repo dir• vmc push --path=target/appassembler

–Start command “bin/<scriptname>”

51

<plugin><groupId>org.codehaus.mojo</groupId>! <artifactId>appassembler-maven-plugin</artifactId>

! ! <version>1.1.1</version>! ! <executions>

! ! <execution>! ! ! <phase>package</phase>

! ! ! ! <goals>! ! ! ! <goal>assemble</goal>

! ! ! ! </goals>! ! ! ! <configuration>

! ! ! ! <assembledirectory>target</assembledirectory>! ! ! ! ! <programs>

! ! ! ! ! <program>! ! ! ! ! ! <mainClass>org.springsource.samples.twitter.Demo</mainClass>

! ! ! ! ! ! </program>


Gradle• Use the application plugin

–Run “gradle installApp”• Creates start script and packages all deps in lib dir• vmc push --path=build/install/<appname>

–Start command “bin/<scriptname>”

52

apply plugin: 'application'

mainClassName = "org.springsource.samples.twitter.Demo"


SBT• Use sbt-package-dist• Creates a zip of all code and deps• vmc push --path=dist/appname/<zipname>.zip

–Start command “java $JAVA_OPTS -jar <main>.jar”

53

plugins.sbt:addSbtPlugin("com.twitter" %% "sbt-package-dist" % "1.0.0")

resolvers += "twitter-repo" at "http://maven.twttr.com"

build.sbt:import com.twitter.sbt._packageDistZipName := "bitshow.zip"

mainClass in Compile := Some("bitshow.Server")


http://maven.twttr.com

http://maven.twttr.com

Eclipse Plugin• Does the packaging for you• Deploy and debug standalone Java apps

–Including Scala and Groovy• Caldecott support

–Tunnel to all services


Practical Tips

Accessing Services


cloudfoundry-runtime• Programmatic creation of service connection factories

–Using ServiceCreator and ServiceInfo classes• CloudEnvironment class

–Access cloud properties–Access service info– No JSON parsing

• Get from the Spring milestone maven repo


Using ServiceCreator in Spring Applications

57

//Provides access to CF service and application env infoCloudEnvironment environment = new CloudEnvironment();! !//Retrieve env info for bound service named "mysqlService"RdbmsServiceInfo mysqlSvc =

environment.getServiceInfo("mysqlService", RdbmsServiceInfo.class);! !//create a DataSource bound to the serviceRdbmsServiceCreator dataSourceCreator = new RdbmsServiceCreator();DataSource dataSource = dataSourceCreator.createService(mysqlSvc);


Using ServiceInfo for all Java Apps

58

//Provides access to CF service and application env infoCloudEnvironment environment = new CloudEnvironment();! !//Retrieve env info for bound service named "mongoService"MongoServiceInfo mongoSvc =

environment.getServiceInfo("mongoService", MongoServiceInfo.class);! !//create a Mongo DB bound to the serviceMongo mongoDB = new Mongo(mongoSvc.getHost(), mongoSvc.getPort());


More Practical Tips...• Use VCAP_APP_HOST and VCAP_APP_PORT env vars

–If not using cloudfoundry-runtime lib• Don’t assign your app a URL unless you plan to bind to the

web port–CF will think your app did not start

• Keep It Alive!–CF will attempt to restart your app if it dies

• Use $JAVA_OPTS in your Java commands–Sets Heap appropriately–Allows debug on local clouds


Key TakeawayEndless possibilities with standalone apps on Cloud Foundry


Demos• Vert.x with SockJS

–https://github.com/cloudfoundry-samples/vertx-socks-sample• Unfiltered with Jetty

–https://github.com/cloudfoundry-samples/cf-unfiltered-sample• WGRUS

–https://github.com/cloudfoundry-samples/wgrus• Spring Batch Workers

–https://github.com/cloudfoundry-samples/spring-batch-tweet-workers


https://github.com/cloudfoundry-samples/vertx-socks-sample




https://github.com/cloudfoundry-samples/cf-unfiltered-sample

https://github.com/cloudfoundry-samples/cf-unfiltered-sample

https://github.com/cloudfoundry-samples/wgrus

https://github.com/cloudfoundry-samples/wgrus

https://github.com/cloudfoundry-samples/spring-batch-tweet-workers




Questions?


Technology

Thinking Outside the Container: Deploying Standalone Apps to Cloud Foundry