The document discusses Platform as a Service (PaaS) selection criteria in 2017 with a focus on the latest information about Heroku. It provides an overview of Heroku's capabilities including processing over 80 billion items daily for over 500,000 developed apps. Examples are given of deploying a Node.js app to Heroku using Git. Key criteria for selecting a PaaS like Heroku are mentioned such as scalability, ease of deployment, and availability of add-ons. The conclusion encourages attending upcoming Heroku events for more information.

1. 再考PaaS
〜 Heroku最新情報で考える、2017年のPaaS選択基準 〜
Mitsuhiro Okamoto
Senior Developer Evangelist
Salesforce.com

2. Statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed
or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-
looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any
statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new,
planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our
service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger
enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These
documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our
Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available
and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features
that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

3. q
q
q

5. •
•
•
•
•
•
•

8. Simplify

9. •
•
•
•

11. 80億件
1日あたりの処理件数
500万以上
開発されたアプリ
150以上
パートナーアドオン
Heroku Platform

22. •
•
•

26. PaaS

34. •
•
•
•
•
•
•

35. •
•
•
•

37. PaaS

40. $ git push heroku master
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 367 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote: NPM_CONFIG_LOGLEVEL=error
…
remote: -----> Building dependencies
remote: Pruning any extraneous modules
remote: Installing node modules (package.json)
remote:
…
remote: -----> Launching... done, v4
remote: https://agile-meadow-8177.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy.... done.
To https://git.heroku.com/agile-meadow-8177.git
777c350..6219ad4 master -> master

41. •
•
•
•
•
•
•
•

44. •
•

47. PaaS

50. ✔
✔
✔
✔
✔
✔

53. アプリのクラスタ化、スケールアウト/アップ

55. •
•
•
https://status.heroku.com

57. •
•
•
•

63. “ Heroku
”
AWS Heroku
•
•
•
Bill Curtis, Co-Founder & CTO, Sweet Tooth

64. https://twitter.com/billcurtis_/status/671466704350797824

65. Heroku
•
•
•

66. 最後に

67. Simplify

68. •
•
•
•
•
•

70. https://herokujp.doorkeeper.jp/events/56274 http://bit.ly/php_heroku_0309

71. thank y u