2015 0228 OpenStack swift; GMO Internet ServicesNaoto Gohko
GMO Internet Inc., has been service provided by the quotient material made of the fact that OpenStack Swift the ConoHa VPS brand and GMO Apps Cloud. discussed the differences between the physical configuration of the OpenStack Swift at rackspace and ConoHa, was carried out optimization of the configuration.
In addition, you have an implementation that provided by Dual-head on multiple merchandise by invoking the swift-proxy for each service.
2015 0228 OpenStack swift; GMO Internet ServicesNaoto Gohko
GMO Internet Inc., has been service provided by the quotient material made of the fact that OpenStack Swift the ConoHa VPS brand and GMO Apps Cloud. discussed the differences between the physical configuration of the OpenStack Swift at rackspace and ConoHa, was carried out optimization of the configuration.
In addition, you have an implementation that provided by Dual-head on multiple merchandise by invoking the swift-proxy for each service.
This presentation vividly describes what is going on in the IT industry with the advent of cloud technology, focusing in Google App Engine. Then reviews competitors’ moves both in terms of background technology and the service capitalization.
It was revealed that major Japanese companies such as Fujitsu and NTT Data are introducing Microsoft Azure in their data centers, but Oracle and IBM are the technically strong chasers. So far there are very few moves
for Japanese IT companies to implement their own cloud products.
IBM's zEnterprise product line has potential to replace and wipe out container-based data centers, but their pricing policy unknown. Oracle's next hardware strategy unknown.
In Japan, tailoring open-source softwares auch as Cassandra and Hadoop found at newly rising companies, IIJ, and Rakuten.
Java EE 7 with Apache Spark for the World’s Largest Credit Card Core Systems ...Hirofumi Iwasaki
Financial companies need Java EE to power its business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 7 for its credit card core systems rearchitecture, from one of the oldest COBOL based mainframe in Japan. Additionally, we chose Apache Spark for super rapid batch execution platform. We completed this big core system migration project successfully.
You can learn why we choose Java EE, and Apache Spark for super rapid batch execution, and our experiences and lessons we learned. How to start such a big project? Why we choose it, how we ported, how use Apache Spark for performance improvements, and launched with? We’ll answer these questions and any that you may have.
Case Study: Credit Card Core System with Exalogic, Exadata, Oracle Cloud Mach...Hirofumi Iwasaki
For increasing business opportunity, the Financial industry companies requires the power, flexibility and scalability of latest enterprise technologies for its 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed their credit card core processing systems utilizing with Java EE. Among the myriad of available technologies, why did we choose Exalogic and Exadata, with Apache Spark distributed configuration? How did we ported from one of the oldest COBOL based mainframe in Japan? What were the key of the success factors into launching and operating this mission critical service? This session unveils our great results, and how our selections are effective for financial enterprise systems.
Consideration points for migrating from older pre-J2EE, J2EE 1.2-1.4, Java EE 5-6 to EE 7, and migration points especially for web front-end systems and back-ends. JSP to JSF, EJB to CDI with migration procedure details. Slide materials on Java Day Tokyo 2016.
Java EE 6 Adoption in One of the World's Largest Online Financial Systems (fo...Hirofumi Iwasaki
Financial companies need Java EE to power its business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. You can learn why we choose Java EE, and our experiences and lessons we learned. This is the first disclosing of a large credit card company in Japan sharing their story.
How to start such a big project? Why we choose it, how we selected the in house development policies, educated ourselves, and developed the additional libraries? How to launch within only six months? What is the key factor driving them as 24/7 critical real financial systems successfully? How to migrate to EE 7 in the future? We’ll answer these questions and any that you may have.
This version is the exclusive session for JJUG CCC Fall 2014 in Japan, binding both JavaOne and OOW 2014 sessions.
Case Study of Financial Web System Development and Operations with Oracle Web...Hirofumi Iwasaki
To stay ahead of the technology curve, financial companies require the power, flexibility, and scalability of latest enterprise technologies for 24/7 services. Rakuten Card, one of the largest credit card companies in Japan, recently renewed its web front-end systems utilizing Java EE. This session provides answers to the following questions: Among the myriad of available technologies, why did it choose Oracle WebLogic and Oracle Exadata, managed by Oracle Enterprise Manager? How did it drive this huge project to completion in only six months, using only in-house development? What were the key success factors in launching and operating this mission-critical service? Hear about its extraordinary improvement results and how its selections are effective for financial enterprise systems.
Java EE 6 Adoption in One of the World’s Largest Online Financial Systems [Ja...Hirofumi Iwasaki
Financial companies need Java EE to power their business today. Rakuten Card, one of the largest credit card companies in Japan, adopted Java EE 6 for its online systems rearchitecture. Learn why it chose Java EE, and hear about its experiences and lessons learned. This is the first time a large credit card company in Japan is sharing its story. How do you start such a big project? Why did it choose Java EE? How did it select the in-house development policies, educate itself, and develop the additional libraries? How did it launch within only six months? What is the key factor driving 24/7 critical financial systems successfully? How do you migrate to Java EE 7 in the future? This presentation answers these questions and any others you may have.
Happy Java 8 release! But for Java EE 7? Is the SE 8 works for EE 7? this slide shows the current situation of applying SE 8 to EE 7. This is the revised version of "JJUG CCC 2014 Spring" session, for the "Java 8 workshop at Fukuoka".
Many enterprise systems build at 2000 - 2010 uses J2EE old specifications with Struts web framework. But nowadays J2EE improved as Java EE, with standard web framework JSF 2. With this slides you can learn how to migrate old-styled J2EE + Struts systems to sophisticated Java EE with JSF 2 specification. This slides was used in Java Day Tokyo 2014 C4 window, presented by the author. And some slides is specialized for Japanese enterprise systems, but the theme is very standard and for almost all J2EE users in the world.
Happy Java SE 8 was released! But for the Java EE?
This materials shows the current status of EE 6/7 with SE 8, and some limitation in current EE 7 app servers with 8.
This session materials is for the Japan Java Users Group (JJUG) CCC 2014 Spring session. #jjgc_ccc #ccc_r11
【DLゼミ】XFeat: Accelerated Features for Lightweight Image Matchingharmonylab
公開URL:https://arxiv.org/pdf/2404.19174
出典:Guilherme Potje, Felipe Cadar, Andre Araujo, Renato Martins, Erickson R. ascimento: XFeat: Accelerated Features for Lightweight Image Matching, Proceedings of the 2024 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR) (2023)
概要:リソース効率に優れた特徴点マッチングのための軽量なアーキテクチャ「XFeat(Accelerated Features)」を提案します。手法は、局所的な特徴点の検出、抽出、マッチングのための畳み込みニューラルネットワークの基本的な設計を再検討します。特に、リソースが限られたデバイス向けに迅速かつ堅牢なアルゴリズムが必要とされるため、解像度を可能な限り高く保ちながら、ネットワークのチャネル数を制限します。さらに、スパース下でのマッチングを選択できる設計となっており、ナビゲーションやARなどのアプリケーションに適しています。XFeatは、高速かつ同等以上の精度を実現し、一般的なラップトップのCPU上でリアルタイムで動作します。
セル生産方式におけるロボットの活用には様々な問題があるが,その一つとして 3 体以上の物体の組み立てが挙げられる.一般に,複数物体を同時に組み立てる際は,対象の部品をそれぞれロボットアームまたは治具でそれぞれ独立に保持することで組み立てを遂行すると考えられる.ただし,この方法ではロボットアームや治具を部品数と同じ数だけ必要とし,部品数が多いほどコスト面や設置スペースの関係で無駄が多くなる.この課題に対して音𣷓らは組み立て対象物に働く接触力等の解析により,治具等で固定されていない対象物が組み立て作業中に運動しにくい状態となる条件を求めた.すなわち,環境中の非把持対象物のロバスト性を考慮して,組み立て作業条件を検討している.本研究ではこの方策に基づいて,複数物体の組み立て作業を単腕マニピュレータで実行することを目的とする.このとき,対象物のロバスト性を考慮することで,仮組状態の複数物体を同時に扱う手法を提案する.作業対象としてパイプジョイントの組み立てを挙げ,簡易な道具を用いることで単腕マニピュレータで複数物体を同時に把持できることを示す.さらに,作業成功率の向上のために RGB-D カメラを用いた物体の位置検出に基づくロボット制御及び動作計画を実装する.
This paper discusses assembly operations using a single manipulator and a parallel gripper to simultaneously
grasp multiple objects and hold the group of temporarily assembled objects. Multiple robots and jigs generally operate
assembly tasks by constraining the target objects mechanically or geometrically to prevent them from moving. It is
necessary to analyze the physical interaction between the objects for such constraints to achieve the tasks with a single
gripper. In this paper, we focus on assembling pipe joints as an example and discuss constraining the motion of the
objects. Our demonstration shows that a simple tool can facilitate holding multiple objects with a single gripper.
4. 4
エンタープライズシステムの歴史
メインフレーム
IBM System/360
1964 1970’s
メインフレーム
IBM System/370
+ 国産互換機
1980’s 1990’s
UNIX System V
+ 商⽤UNIXs
Stratus
ノンストップ “ミニコン”
Tandem
2000’s 2010’s
Windows NT+IIS
Linux
J2EE 1.2
アプリ
サーバー
Netscape
WebLogic
.NET
Framework
.NET Core
Java EE 5 Jakarta EE 8
2020’s
?
CORBA
XA
5. 5
J2EE à Java EE à Jakarta EEの歴史とEclipse MicroProfileの分岐
2000
J2EE 1.2 J2EE 1.3 J2EE 1.4 Java EE 5 Java EE 6 Java EE 7 Java EE 8 Jakarta EE 8
2001 2003 2006 2009
Eclipse MicroProfile
2016
MicroProfile
1.0
2013 2017
2018 2Q
MicroProfile
2.0
MicroProfile
3.0
2019 2Q
2019
分岐
12. 12
Jakarta EEとEclipse MicroProfileとの違い
準拠アプリケーションサーバー
Java VM
EAR, WAR, EJB-JAR
アプリケーション
1. BOOT
2. DEPLOY
Java VM
フレームワーク
JAR アプリケーション
1. BOOT
Jakarta EE
(コンテナー型)
Eclipse MicroProfile
(フレームワーク型)
on
Other
Apps
アプリケーションサーバーへ配備して動作 ⾃⼒で動作
24. 24
まとめ
1. Jakarta EE と MicroProfile は別々に動いている別のプロジェクト
à 異なるパッケージ名、後⽅互換性の考え⽅、認証プロセス、権利関係等
à 合流は現状難しい感触 (Oracle Code One 2019, Eclipse Con Europe 2019)
2. 「アプリケーションコンテナー」型 (Jakarta EE)
対「フレームワーク」型 (MicroProfile)
à どちらも美点と⽋点あり。どちらかに寄せることは難しい
à 基幹系・⾼負荷リアルタイム処理にはコンテナー系、Web系View
Controller・バッチ系にはフレームワーク型など、使い道に応じて採⽤を個別検
討するのが得策
3. Eclipse MiroProfileは未完のフレームワーク仕様である
à ⾜りない分は⾃分で考えて追加する必要あり。今後どうなっていくのか不明。
à ベンダーロックインの可能性あり。注意!!