Premier developer event opens speaker proposals
San Francisco, December 15, 2016 — Cloud Foundry Foundation today announced its call for papers has opened for Summit Silicon Valley 2017, which will take place June 13-15 in Santa Clara, CA. Early Bird Registration and a speaking call for papers (CFP) are now open for the event. Sponsorship opportunities are available now for members only. Non-members will be given the opportunity to sponsor starting January 3, 2017.
Cloud Foundry Summit Silicon Valley is the premier event for enterprise application developers. The event will focus on microservices and continuous delivery in all frameworks.
Premier developer event opens speaker proposals
Pushing Apps to Cloud Foundry is as easy as it gets, thanks to the cf push command. However, it is still tedious to push your code after every change you make, just to see if it runs in the cloud. That’s where a CI/CD (continuous integration and continuous deployment) server comes in handy. It tests, builds and deploys your code every time you git push changes and makes sure that your code is always tested and deployed.
Now wouldn’t it be nice if your CI/CD server which deploys to Cloud Foundry also actually ran on Cloud Foundry? With Strider that is possible. It watches all your repos and, as soon as you git push some changes, tests them and deploys your app to CF.
In the previous blog Scaling Real-time Apps on Cloud Foundry Using Node.js and Redis, we used Redis as a ‘session store’ and also as a ‘pub-sub’ service for chat messages. But in many enterprise grade real-time apps, you may want to use RabbitMQ instead of Redis to do pub-sub because of the reliability and features that comes out-of-the-box in RabbitMQ. This is especially true for financial or Bank apps like Stock Quote apps where it is critical to protect and deliver each-and-every message AND do it as quickly as possible.
So, in this blog, we will start from Scaling Real-time Apps on Cloud Foundry Using Node.js and Redis and simply replace Redis with RabbitMQ pubsub.
In Part II of this series, we covered the architecture needed for persisting the Activity Streams to MongoDB and fanning it out in real-time to all the clients using Redis PubSub.
Since then, some exciting new Node.js features for Cloud Foundry were launched. In addition, the MongoDB version on Cloud Foundry has been upgraded to 2.0.
In this blog post we will cover how to:
Use Mongoose-Auth to store basic user information, including information from Facebook, Twitter, and Github, and how we made this module with native dependencies work on Cloud Foundry
Use Mongo GridFS and ImageMagick to store user uploaded photos and profile pictures
Perform powerful stream filtering, thanks to new capabilities exposed in MongoDB 2.
Cloud Foundry has long supported auto-reconfiguration for Spring and Ruby applications. Now we are pleased to add auto-reconfiguration support for Node.js applications as well. Deploying Node.js applications to Cloud Foundry previously required parsing of environmental variables and overwriting server and service connection function calls to use Cloud Foundry specific parameters. This approach was not intuitive to developers who just started to use Cloud Foundry to deploy their applications. They would need to consult the documentation and figure out what port and host they need to connect to. Moreover, if an application uses services, developers would need to configure their applications to use the proper service connection parameters.
Most real-world applications we ship to consumers or enterprises are multi-year projects. In the cloud era, newer technologies (programming languages, runtimes, frameworks) are created faster than ever. While most of them fail to get any traction, once in a while a technology becomes popular because it solves a problem or set of problems extremely well.
Now in such an era, if you make a large investment for a multi-year project on a PaaS that only supports one technology and some other technology comes along that happens to solve your problem better, then you are stuck. You have unintentionally become a victim of vendor lock-in. The heart of your problem is that your PaaS, and hence your app, was not future-proofed to begin with.
In Part I of this series, we showed how to start from the node-express-boilerplate app for real-time messaging and integration with third parties and move towards building an Activity Streams Application via Cloud Foundry. The previous app only sent simple text messages between client and server, but an Activity Streams Application processes, aggregates and renders multiple types of activities. For this new version of the application, my requirements were to show the following:
User interactions with the app running on CloudFoundry.com
Custom activities created by users on the app’s landing page
User activities from GitHub such as creating repositories or posting commits
For this reason, I decided to use Activity Strea.
Cloud Foundry provides developers with several choices of frameworks, application infrastructure services and deployment clouds. This approach to providing a platform as a service enables the fast creation of useful cloud applications that take advantage of polyglot programming and multiple data services. As an example of how this enables us to be more productive, I was able to use Node.js, Redis, and MongoDB to create an Activity Streams application in a short time, despite the fact that I mainly develop Web Applications in Ruby. Based on the developer interest after a demo of this application at NodeSummit 2012 and MongoSF 2012, I was inspired to do a 3 part blog series that fully details the creation, deployment, and scaling of this application on CloudFoundry.com.
Cloud Foundry has supported Node.js from day one. Today we are delighted to announce Joyent will become the Cloud Foundry Community Lead for Node.js. Community Leads bring deep experience and passion for specific technologies to Cloud Foundry. Joyent will contribute and maintain Node.js support for Cloud Foundry, providing ongoing updates, direction and community engagement. As the open source project owner and home to Node’s core team, Joyent has invested heavily in making Node the leading runtime for data-intensive real-time mobile and web applications for the individual developer and the enterprise.