JavaOne 2016 Report for JavaEE

いいね！ 3
閲覧回数 449
ダウンロード数 19

This is a report for JavaOne San Francisco 2016. It explained the current status and future plan of Enterprise Java especially Java EE 8/9 and Microprofile.

コメントの公開にはサードパーティサービス Disqus を使用します。Disqus に登録していれば誰でも会話に参加できます。

Docs.com とは

JavaOne 報告会Java EE の今後についてYoshio TeradaSenior Java EvangelistYoshio.Terada@microsoft.com@yoshioterada自己紹介　 Java エバンジェリスト　 Java チャンピオン　日本マイクロソフト (株 ) 　寺田　佳央　ハッシュタグ #てらだよしおがんばれ日本企業が JavaOne 基調講演で数多く登壇富士通日立NEC損保ジャパン日本興亜Mazda：数村様：村上様：岸上様：浦川様：吉岡様https://javaee-guardians.io/https://javaee-guardians.iohttps://javaee-guardians.io// 火星のお話よりも不安を払拭するため基調講演でもう少し Java EE に時間を掛けるべきでしたブレークアウト・セッションの参加で不安は払拭 !! 戦略的には良い方向へ !! ( 詳細はのちほど)でも、べつの不安が !!September 22, 2016Hilton San Francisco Financial Districthttps://microprofile.io/https://microprofile.iohttps://microprofile.io//ベンダー＆コミュニティが集結背景各ベンダーの個別会話からはじまったJava EE GUARDIANS もひとつのきっかけ既存の Java EE 技術におけるマイクロ・サービス対応WildFly SwarmWebSphere LibertyPayaraTomEEプロジェクトはすでに Java EE & 非 Java EE 技術を活用マイクローサービス対応の新機能を構築中参加者すべてが市場への早期投入を重要視Java EE をより良く、より早くMicroProfile リリースの哲学反復 (アジャイル )イノベーション開発における総意リリース 1.0標準化標準化には時間を要す !!開発のすすめ方・戦略は MicroProfile の方が時代に適応 !! (個人的に支援 )MicroProfile.io or/and Java EE 8/9戦略的には良い !!ここに記載する内容はあくまでも提案内容 (未決定 ) !!Cloud Micro Service２年前と世界が変わったクラウド化・マイクロサービス化マイグレーション・パスを用意Java EE の後方互換性を維持REST(JAX-RS) は今後重要Java EE Spec Lead(Linda DeMichel)Java EE 9 がメインJava EE 8Java EE 9 への準備Java EE 9クラウド & マイクロサービス同時に開発を進行Java EE 8 の提案内容リアクティブプログラミングリアクティブ宣言http://www.reactivemanifesto.org/jaリアクティブ宣言即応性 (Responsive )耐障害性 (Resilient )弾力性 (Elastic)メッセージ駆動 (Message Driven)リアクティブ・プログラミングレイテンシ向上のために必要非同期処理ノン・ブロッキング I/OJava EE 8 は EE 9 への移行パスJava EE 9 で最終的に対応Java EE Spec Lead(Linda DeMichel)JAX-RS 2.1 : クライアント側の大幅な更新リアクティブ・プログラミング非同期処理の改善 : 実装方法の改善Non-Blocking 対応 : リソース消費を防ぐためService AService BService CService DService BService AService CService DJAX-RS 2.0 の非同期処理( コール・バック地獄)JAX-RS 2.1 : CompletableFuture<T> を利用非同期処理をより簡単にRxJava も利用可JAX-RS 2.1 : Non-Blocking 対応非同期 ( Async ) 処理は新しいスレッドを生成するだけ　処理結果が返ってくるまでブロック– NioInvoker– NioWriterHandler– NioOutputStream extends OutputStream待ち状態のリソース消費を防ぐヘルス・チェック : 新 JSRService AService B生死監視用の REST API を定義 (JSON フォーマット )設定変更可能なパスを定義 (/ healthcheck )ブートストラップ・エンドポイントを用意ヘルスチェック用のエンドポイントを取得可能例： /management/endpointアノテーションでエンドポント実装可能エンドポイントの URL マッピングも作成可能レポート用のヘルパークラスを用意ヘルス・チェック : 新 JSRService AService B適用範囲は実装依存アノテーション (記述子 )で指定されたクラスだけが対象実装に応じてシステム情報も取得可能例：ドメイン、サーバ、クラスタ、パーテション・テナント、ロードバランサ、マイクロサービスなどセキュリティ要件は実装依存認証済み、アクセス制御のリソースへのヘルスチェックConfiguration - 外部設定Service Aプロパティ , XML, JSON フォーマットをサポート複数の設定ソースをサポート階層化とオーバライドをサポートオプションの設定スキーマポーリングと動的プロパティ動的設定変更が可能 ( Archaius を参考 )Configuration - 外部設定Service AConfiguration 実装例マルチテナンシー対応テナントによる特定のカスタム UI の提供例：テナント毎に変更するロゴなど実行時に JSF ベースの US 構成テナント毎のデータソース例：テナント毎に異なる DBテナント毎のセキュリティマルチテナンシー対応 - テナント・コンテキストリクエストに対し TenantContext オブジェクトを埋め込むテナントとコンテナを関連付けさせTenantContext はテナントを識別する情報を保持例：テナント ID などTenantContext はアプリケーション内で利用可能コンテナはテナント毎の処理を実行可能マルチテナンシー対応 - インタフェース public interface TenantContext{ public String getTenantID(); public String getTenantName(); public void setProperty(String name, String value); public String getProperty(String name); public Map<String, String> getProperties(); }マルチテナンシー対応 - データ・アクセス@MultiTenant アノテーションを宣言テナントは、分割された独自のデータを保持他のテナントからは保護テナント毎の DB に接続するため TenantContext を利用ネーミング・サービスを利用DataSource の API も拡張予定自動的にデータ・ソースに接続セキュリティ – JSR 375 標準用語の作成認証メカニズム用の APIID ストア用のAPIセキュリティ・コンテキスト用 APIJava EE 8 で対応( クラウド対応に必要)認証 – OpenID Connect認可 - ロール・権限秘密管理（パスワード・エイリス）認証用インタセプターJava EE 9 で対応( マイクロサービスで利用)Java EE 9 マイクロ・サービスSpec Lead 歴JSR-250 : Common AnnotationsJSR-224 : JAX-WS 2.0 JSR-315 : Servlet 3.0JSR-340 : Servlet 3.1Rajiv Mordaniマイクロサービス開発の標準にしたいアプリはベンダー間で移植可能既存のベンダーと共同作業したい開発者の共通課題を標準化したいRajiv Mordani Micro Service今まで：モノリシック (一枚岩 )(Enterprise Application)利点：　一つのファイルにパッケージ化可能　テストが容易　開発が容易欠点：　新機能追加・修正が困難頻繁なデプロイが困難 (再度全テスト ) 一つのサービスの変更が全てに影響一つのサービスの負荷が他に影響一つのサービスの停止が他に影響　新フレームワークの導入も困難UIロジックDBロジックUIDBwar, ear ファイルJava EE (App Server)Java VMマイクロサービスのアプローチ : 疎結合利点：　サービスやシステムの変更に柔軟　一つのサービス変更は他に未影響　サービス毎のスケールが可能　単一サービスの停止は他に未影響　サービス毎に柔軟なフレームワーク選定可能欠点：　 (分散 )サービス間連携の構成検討が困難　運用・管理などの操作数が増加（高度な自動化）UIUIロジックロジックDBDBService AService Bマイクロサービスを意識した Java F/W標準的な実装がない開発者が選択 -> 標準化Java EE 9 のアーキテクチャ案マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain Eventsマイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsAPI Gatewayマイクロサービスの主要な技術の一つAmazon, Kubernetes, Marathon, Microsoft 等もサポート全クライアントがアクセスする唯一のエントリポイントアクセス制御プロトコル変換コンテント集積リソース・キャッシュログMobileClientService AAPIGatewayService BBrowserClientAPIGateway※ クラウド/PaaS プロバイダが提供 (Java EE 9 未対応)マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsService Registory/Discovery動的変化するサービス・エンドポイントへの接続10.0.1.1:808010.0.1.1:8081Service AService A10.0.1.2:808010.0.1.2:8083Service BClient10.0.1.3:808210.0.1.4:8085Service CService Registory/Discovery1. 接続先情報を Service Registory に登録Service Registory/DiscoveryService AIP アドレスPort 番号を登録Service A①Service BClientService CService Registory/Discovery2. 接続先の情報を問い合わせRegistory/DiscoveryServerService AService ALB が接続先のIP アドレスPort 番号を取得Load Balancer②Service BClientService CAPIGatewayService Registory/Discovery3. 取得した情報を元にサービスに接続Registory/DiscoveryServerService AService ALoad Balancer取得した情報を元にLB はサービスに接続③Service BClientService CAPIGatewayService Registory/DiscoveryJava EE 9 の実装提案Inject/Auto-Wiring を使用しクラウド・サービスを発見依存するサービスを発見するための一環した名前を定義クライアント・サイド Discoveryクライアント・サイドのコードはロードバランサで使用例： Netflix Eureka, Ribbonサーバ・サイド Discoveryサーバ側で発見しロードバランスを実施ルータが Service Registory に問い合わせクライアントはサービス・ルータを経由しリクエスト送信例： AWS Elastic Load Balancer, Malathon LBService Registory/Discoveryクライアントの Service Discovery 方法開発者は標準定義が必要例：サービス名＋バージョン＋名前空間 HttpClient.connect(“http://localhost:8081”); HttpClient.connect(“http://service_dns.example.com”); //Spring の場合 DiscoveryCllient getInstance(“SERVICE-NAME”);Service Registory/DiscoveryService Discovery 方法メタデータを設定サービス名、互換性バージョン、実装バージョン、依存関係 @InternalService @Service(name=“userProfiles”,compatibilityVersion=“1.2”) @Depends(services={“userAvatars:2”,”userAddresses:5”}) public ProfileData getUserProfile(ID userID){ }マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain Eventsサーキット・ブレーカーサーキット・ブレーカー特定サービスの遅延・障害時にも全体サービスを継続Service AService ALoad Balancer待ちによるスレッドの滞留を防ぐService BClientService CAPIGatewayサービスの切り離しと回復BulkHead ( 隔壁) パターン並列 (スレッド )のサービス呼び出し数を制限浸水により船が全体沈まないように守る壁高負荷 DBの呼び出しで大量の待ちが発生全体がハングするのを防ぐService AService Bサーキット・ブレーカーJava EE 9 の実装提案JAX-RS Client API を拡張専用アノテーションを提供 : 再試行ポリシー、回復ポリシー、障害時に呼び出すメソッド定義など動的な設定が可能リアクティブのプログラミング・モデルリクエスト・レスポンスのキャッシュグラフィックによるサービスの依存性と実行状況の表示※ ヘルス・チェック機能は Java EE 8 で実装サーキット・ブレーカー実装例 public class Foodservice { @RetryPolicy(delayPeriod=10 unit=SECOND, numRetries=1) 　 @CircuitBreaker(fallbackMethod= “getBooksByAuthorFallBack”) @BulkHeadPolicy(threadCount=5) public Collection<BooK> getBooksByAuthor( String authorName){…} public Collection<Book> getBookdsByAuthorsFallBack(){…} }Spring+Netflix の場合の例項目利用する機能 (サービス）設定管理Spring Cloud Config + Busサービスの登録・発見Netflix EurekaロードバランサNetflix Ribbonサーキット・ブレーカーNetflix Hystrix + TurbineProxy ServerNetflix Zuul認証Spring Cloud Securityマイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsRDB 以外も様々な永続ストレージ対応Service AKey/Value StoreService BDocument DBColumn DBService CGraph DBService DNoSQL 関連ストレージ対応ベンダー依存の API を利用NoSQL 関連ストレージ対応NoSQL 対応Java EE 9 の実装提案javax,persistence.nosql パッケージを定義一貫性のあるプログラミングモデルを提供CROUD 操作に対する共通の抽象化したAPI を提供ベンダー独自機能への直接アクセスも可能クエリの簡素化メソッド名によるクエリの推論ベンダー独自クエリアノテーション機能ごとにカテゴライズしたアノテーションREST 経由でも利用可能NoSQL 対応 package javax.persisntece.nosql; import java.util.Iterator; public interface CROUDStore<K extends ID, V extends BaseStore<K,V>{ Iterator<V> findAll(); V find(K key); V persist(V value); void remove(K key); void remove(V value); }カテゴリ指定 (Key/Value の例）CROUDStore を拡張した KVStore の実装提案 public interface KVStore<V> 　　 extends CROUDStore <ID<String>, V >{ void persist(ID<String> key, V value); }有効期限を設定可能な KVCacheStore の実装提案 public interface KVCacheStore<V> extends KVStore<V>{ void persist(ID<String> key, V value, long expires); void expire(ID<string>key, long expires);}カテゴリ指定 (Key/Value の例）MongoStore を拡張した UserStore の定義例 public interface UserStore extends MongoStore<String, User>{ List<User> findBynameStartingWith(String regexp); List<User> findByLastnameEndingWith(String regexp); @Query(“{‘age’ : { $gt: ?0 , $lt: ?1}}”) List<User> findUsersByAgeBetweeen(int ageGT, intageLT); }カテゴリ指定 (Key/Value の例）MongoStore を拡張した UserStore の定義例 public class UserStoreIntegrationTest{ @Inject UserStore userStore; public void insertUser(){ final User user = new User(); user.setName(“Jon”); userStore.persist(user); List<User> users = 　　 userStore.findUsersByAgeBetween (5,10); …} }マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsCQRS : データの参照と更新を分離今までの DB 操作 CQRS による DB 操作更新更新サービス更新アプリ参照 (クエリ )参照 (クエリ )参照サービス参照と更新処理は異なりスケールの観点でも分離が重要CQRS 対応 : 実装方法は EG と検討中Java EE 9 の実装提案CQRS を状態管理でも利用可能エキスパート・グループと今後会話予定CommandsDomain EventsDomain Event HandlersEvent Storeマイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsTolerant Reader : ( 寛容な読み込み)バージョンが変わった際のデータ (JSON)・スキーマの変更で呼び出し側が破壊されないようにService A(ver1)Service 1Service A(ver2)Service 2Service A(ver3)実装者が考慮する内容 (Java EE 9未対応 )マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsChained & Branch Service同期型、もしくは非同期で依存するサービスを呼び出しService AService BService CService DChainedService BService ABranchService CService D実装者が考慮する内容 : Java EE 8 JAX-RS 2.1 で追加・改良マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsAsynchronous Messaging ( メッセージ駆動)数百万 Req /Sec のイベントを取得しアプリに配信Azure Event Hub新しいストリーム・イベント用 API を定義Asynchronous Messaging ( メッセージ駆動)メッセージ駆動 (Message Driven) @Inject EventPublisher(“mytopic”) publisher; @Inject EventConsumer(“mytopic”) consumer;任意のメソッドをイベント・リスナーとして実装可能 @EventListener(“mytopic”) public void onMyEvent(MyEvent event){ //doSomething; }マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain Eventsメッセージ駆動 (Message Driven)Java EE パッケージJava SE 9 のモジュール機能 (Jigsaw) を利用移植可能なアプリマイクロサービスを簡単にすばやく作れる任意の Java EE 9 環境にデプロイ可能コードJava EEKey APIMyApp.jarRuntimeJava SEService Instantiationメッセージ駆動 (Message Driven)サービスがどこで稼働しているかわからない (ホスト・コンテナ )ホスト 1Service Aホスト 1/コンテナService AService BREST 呼び出しコンテナ２Service BREST Call のネットワーク負荷考慮型基本型メッセージ駆動 (Message Driven)Service のプロビジョン方法の提供Java EE 9 の提案共通メタデータの標準化名前・バージョンCPU, メモリリソースの依存関係現在様々なフォーマットYAML, JSON などMethos, Kubernetes の例メッセージ駆動 (Message Driven)Service のグルーピング方法の提供Java EE 9 の提案グループ化の標準化グループでスケールKubernatis の PodMethos, Kubernetes の例マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain EventsConsumer-Driven Contractsメッセージ駆動 (Message Driven)サービス間の結合テストサービスの実装更新による結合破壊を防ぐサービスの提供者側と利用者側で規約 (契約書 )を作成Service B (v1)Service AService B (v2)※ 実装者が検討・考慮する内容 (Java EE 9 未対応)マイクロサービス・デザイン・パターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain Events Domain Event (Event Sourcing : Eventual Consistency) メッセージ駆動 (Message Driven)データの永続化やサービスの呼び出しに対する結果整合性 ( eventual consistency ) が必要　トランザクションによる実装ではなく、複数のサービス間でのトランザクションを実装するため、イベントベースでの実装Service AService B各サービスで重複登録など整合性を確認Cach / Messaging / Event System Domain Event (Event Sourcing : Eventual Consistency) メッセージ駆動 (Message Driven)Java SE 9 の提案オブジェクト・ベースの状態共有モデルベンダーに非依存実装方法の詳細 (クラス・パッケージ )は検討中様々なデータ・ストアを利用可能？Cache, Messaging/Eventing, JPA + DBJava EE 9 で対応予定のパターンAPI GatewayService Registry / Service DiscoveryCircuit BreakerPolyglot PersistenceCommand Query Responsibility Segregation (CQRS)Tolerant ReaderChained ServicesAsynchronous MessagingService InstantiationConsumer-Driven ContractsDomain Eventsその他クラウド・プロバイダが提供するサービスへ接続可能Java SE 9 の提案クラウドプロバイダが提供するサービスインジェクト可能設定サービス、イベント、状態 /キャッシュ /DBはサービスなどアノテーションもしくはメタデータ・ドリブン public class MyService{ @EventService() EventService eventService; public void foo(){ eventService.subscribe(“StateChanges”); } } @ConfigService(namespace=“Srv”) ConfigService configService; Auto ScaleJava SE 9 の提案アノテーションでインスタンスの数を指定自動的に現在の数を調整Auto Scale ポリシーの設定CPU 消費メモリ消費リクエストのルーティング情報カスタムのメトリック予測スケジューリング動的なスケーリング・ポリシーの（サービス・機能）設定 Auto ScaleJava SE 9 の提案ポリシーの例全インスタンスのうち 75%以上の使用率が 3分続くとスケールアウト全インスタンスの使用率が 90%以上でスケールアウト全インスタンスの使用率が 15分間 20%より下回ればスケールバック平均使用率が 40%以下、インスタンス数が 6以上でスケールバックインスタンス数の最小、最大の数を指定可能スケジュール・ベースでスケール設定が可能 Java SE 9 のリアクティブ対応リアクティブ用の包括的な API を提供Publish/ Subscriber APIPublisher で既存のデータ構造(Itterable,Arrays など) を利用可能イベントのストリーム処理用の操作 APIを提供バックプレッシャーをハンドルするための API を提供改良したエラーハンドリング・メカニズムを提供イベント・ストリームの相互運用性JDK 9 の Flow API を利用他のリアクティブ実装もプラグイン可能参考情報 (私がつけた優先順 )セッション番号タイトルCON7976Java EE 8 UpdateCON7975Enterprise Java for the CloudCON8292Portable Cloud ApplicaHons with Java EECON7983JAX-RS 2.1 for Java EE 8CON7977Java EE Next – HTTP/2 and RESTCON7980Servlet 4.0: Status Update and HTTP/2CON7979Configuration for Java EE 8 and the CloudCON7978Security for Java EE 8 and the CloudCON1558What's New in the Java API for JSON BindingCON4022CDI 2.0 Is ComingCON7981JSF 2.3BOF7984Java EE for the Cloud参考情報Java EE 8 の動画　https://www.youtube.com/watch?v=Th9faGLhQoM httpshttps://www.youtube.com/watch?v=Th9faGLhQoM ://https://www.youtube.com/watch?v=Th9faGLhQoM www.youtube.com/watch?v=Th9faGLhQoMJava EE 9 の動画　 1 . Enterprise Java for the Cloud　　https://www.youtube.com/watch?v=t7miysQP7Dg httpshttps://www.youtube.com/watch?v=t7miysQP7Dg ://https://www.youtube.com/watch?v=t7miysQP7Dg www.youtube.com/watch?v=t7miysQP7Dg　 2 . Portable Cloud Applications with Java EE　　https://www.youtube.com/watch?v=nCqVSf5v37s httpshttps://www.youtube.com/watch?v=nCqVSf5v37s ://https://www.youtube.com/watch?v=nCqVSf5v37s www.youtube.com/watch?v=nCqVSf5v37sMicroProfile のイベント動画　https://www.youtube.com/watch?v=6emPnRChsEE https://www.youtube.com/watch?v=6emPnRChsEE　発表資料　http://www.slideshare.net/rayploski/microprofile-panel-sept-2016 http://http://www.slideshare.net/rayploski/microprofile-panel-sept-2016 www.slideshare.net/rayploski/microprofile-panel-sept-2016フィードバックは 2016/10/21 (金 )までhttp://glassfish.org/surveyhttp://glassfish.org/surveyWhere to go?今どちらが良いか分かりません各社が会話し良い方向に進むことを期待しますマイクロサービス on Microsoft AzureAzure Service FabricMicrosoft AzureCognitiveServiceIBM さんの基調講演Java をもう一度素晴らしい物にしましょう by IBM さんCognitive Service と JAX-RS でより良い社会・未来をつくりましょう！！インフラエンジニア、アーキテクト、 IT 戦略立案に関わる皆様を対象にクラウドを活用したビジネスのデジタルトランスフォーメーションに必要なマイクロソフトの最新技術情報と実践的ノウハウをご紹介します2016 年 11 月 1 日 ( 火) – 11 月 2 日 ( 水) ヒルトン東京お台場http://microsoft-events.jp/mstechsummit/http://microsoft-events.jp/mstechsummit/ JavaOne 報告会Java EE の今後についてYoshio TeradaSenior Java Evangelistyoterada@microsoft.com@yoshioterada© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.d. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes

JavaOne 2016 Report for JavaEE

興味のある情報を集め、整理して、みんなと共有しましょう。

読み込んでいます...