Japan Developer Summit (jp) - Cloud Foundry, the Open Platform As A ServicePatrick Chanezon
?
This talk will provide an overview of the PaaS (Platform as a Service) landscape, and will describe the Cloud Foundry open source PaaS, with its multi-framework, multi-service, multi-cloud model.
Cloud Foundry allows developers to provision apps in Java/Spring, Ruby/Rails, Ruby/Sinatra, Javascript/Node, and leverage services like MySQL, MongoDB, Reddis, Postgres and RabbitMQ.
It can be used as a public PaaS on CloudFoundry.com and other service providers (ActiveState, AppFog), to create your own private cloud, or on your laptop using the Micro Cloud Foundry VM.
I will describe the Cloud Foundry architecture, and talk about the open source development process for Cloud Foundry.
ngGoBuilder and collaborative development between San Francisco and Tokyonotolab
?
This document discusses ngGoBuilder, a game engine and set of tools for developing games using ngCore. It describes ngGoBuilder 1.x features like scrolling layers and particle effects. It then discusses plans for ngGoBuilder 2.0 which will focus on a better user experience and include ngCore, debugging tools, and sample games. Future roadmaps include improved animation support and integration with the ngServer platform. The document also covers collaboration between the San Francisco and Tokyo teams working on the project.
The document discusses ngServer, a server-side framework powered by Node.js that was created by DeNA for building social games. It describes ngServer's architecture which uses Express for routing and handles authentication, rendering, jobs, and interfacing with social APIs, memcache, data stores, and queues. It also covers ngServer's functions like commands, templates, profiling, deployment across multiple servers, and challenges of building for an international audience.
ngGoBuilder and collaborative development between San Francisco and Tokyonotolab
?
This document discusses ngGoBuilder, a game engine and set of tools for developing games using ngCore. It describes ngGoBuilder 1.x features like scrolling layers and particle effects. It then discusses plans for ngGoBuilder 2.0 which will focus on a better user experience and include ngCore, debugging tools, and sample games. Future roadmaps include improved animation support and integration with the ngServer platform. The document also covers collaboration between the San Francisco and Tokyo teams working on the project.
The document discusses ngServer, a server-side framework powered by Node.js that was created by DeNA for building social games. It describes ngServer's architecture which uses Express for routing and handles authentication, rendering, jobs, and interfacing with social APIs, memcache, data stores, and queues. It also covers ngServer's functions like commands, templates, profiling, deployment across multiple servers, and challenges of building for an international audience.
The document discusses the "Heroku Way" of building modern web applications. It outlines 7 aspects that Heroku considers essential: codebase, dependencies, config, backing services, build/release/run processes, processes, and logs. Each aspect is broken down into further details around how applications should be structured on Heroku for easy deployment and management. The Heroku Way aims to allow developers to focus on their application code rather than infrastructure concerns like deployment by adopting its best practices for 12-factor apps.
This document contains several links to resources about metrics-driven engineering, growth forecasting, log analysis, and presentations. It also includes examples of commands for provisioning and testing a database server, and APIs for retrieving node information. Overall, the document shares various references and code snippets related to operations, monitoring, and infrastructure automation.
The document discusses Tomoharu Nagasawa's presentation on developing engineering skills that will still be relevant in 10 years. It emphasizes continuous feedback and Visual Studio "11" as keys to an enduring development environment. Nagasawa is an evangelist at Microsoft who focuses on agility, communities, and tools.
1) The document discusses the gap between theory taught in textbooks and real-world practice.
2) It notes the difference between a "closed world" of textbooks and an "open world" of practical application, and argues one must be prepared to face the open world.
3) The document suggests principles and practices can help bridge the gap, and that maturity involves moving from principles to adapting them based on experience.
The document discusses App Inventor, a visual programming tool developed by MIT to allow users to build Android apps without coding. It notes that App Inventor was launched in 2011 as an open source project from Google Labs and is now maintained by MIT. The presentation provides an overview of App Inventor and its use in education and app development.
The document discusses Android 4.0 and design. It covers UI changes in Android 4.0 including a unified look across screen sizes. It discusses new APIs, compatibility modes, and handling hardware menu buttons in Android 4.x. The document provides links to developer guides on these topics.
The document discusses expanding experiences through sharing and the possibility of flying in the sky. It is signed by Ichitani Toshihiro from Developer Summit 2012 representing Eiwa System Management Inc. and dated February 16, 2012.