From http://www.csdn.net/article/2015-12-17/2826501
《数美公司联合创始人兼CTO梁堃:Sentry金融实时风控系统》
数美公司联合创始人兼CTO梁堃在主题演讲中介绍了Sentry金融实时风控系统。他表示实时风控系统对于银行业继续保持高速发展越来越重要。Sentry金融实时风控系统是基于大数据技术构建的实时交易风险评估系统。其工作过程是,在每一笔交易发生时,实时进行(1)业务系统将交易信息发送风控系统;(2)发现该交易中存在的异常行为和可疑场景;(3)根据发现的“证据”计算该交易的风险系数;(4)将风险系数等相关信息反馈给业务系统。
The opportunity and challenge of Enterprise Ceph - Jiaju Zhang, Gao MingxingCeph Community
?
Cephalocon APAC 2018
March 22-23, 2018 - Beijing, China
Jiaju Zhang, Red Hat Chief Solution Architect, Ceph Community member
Gao mingxing, China Railway Information Technology Center Technical Support Minister
The product release plan outlines the company's planned releases of hardware and software products over the next few quarters. It includes the scheduled release of new workstation hardware and software, edge hardware and software, AI edge devices, vision and IoT kits, tools, and new Alpha workstation models. The plan provides a quarterly roadmap for introducing new products from Q3 to Q2 the following year.
This document discusses using an M48X MCU and Jetson Nano for a home automation project. The M48X MCU controls lights and other devices via UART commands from a Jetson Nano or PC. Example commands are given to turn lights on/off, change colors, and start automated light shows or routines. Additional commands allow controlling videos, music and messages played on the Jetson Nano through the M48X MCU.
This document describes the design of an autonomous guided vehicle (AGV) system. It outlines the main components including the order system, dispatcher, universal clock, AGVs, broker, grid map database. It then describes the functions of various components like the naive dispatcher, path planner using A* algorithm, discrete time simulation with the universal clock, AGV main flow, grid map GUI, and traffic control strategies to handle conflicts between AGVs.
The document discusses microservices and provides definitions, examples, and considerations around this architectural style. It defines microservices as small, independent processes communicating via APIs to compose complex applications. It notes microservices allow for increased modularity, independence, and scalability compared to traditional monolithic architectures. The document also shares perspectives from experts on microservices and examples of companies using this approach.
20160217 - Overview of Vortex Intelligent Data Sharing PlatformJamie (Taka) Wang
?
Vortex Intelligent is an intelligent data sharing platform that provides several product suites including Vortex OpenSplice, Vortex Starter Kit, and Vortex Device. Vortex OpenSplice is a DDS library that implements DDS 1.2 and DDSI 2.1 standards. It has both free and paid versions. Vortex Starter Kit and Vortex Device target different developer types. Additional products like Vortex Insight, Vortex Cafe, Vortex Web provide visualization, Java DDS library, and JavaScript DDS library capabilities. Vortex also includes options for cloud, fog, and gateway integration.
This document discusses strategies for IoT development. It proposes three levels of architecture - short, mid, and long term - to develop an IoT kernel and services. It also examines Advantech's IoT products and architectures, including their WebAccess SCADA system and WISE-Cloud platform. Challenges in IoT solutions are identified around connectivity, costs, reliability and time to market. Two proof-of-concept projects are proposed using edge cloud services and Modbus TCP.
This document discusses microservices architecture and how Docker has changed application development. It covers:
- The rise of microservices architecture which breaks applications into independently deployable small services.
- How Docker brings development and operations teams closer together through standardized deployment of services.
- How Docker provides consistency for continuous integration testing by allowing identical environments.
- How Docker enables collaboration through sharing of pre-built application containers.
This document summarizes the design of a proactive service. The key aspects covered include:
1. The service uses microservices architecture with services like modbusd, psmb-srv, and azure-srv. It follows design principles of pluggable packages, test-driven development, and API-first design.
2. Configuration is handled through environment variables, JSON/YAML files, or a remote configuration server. Services discover each other through Consul.
3. Logging is done through a structured logger that supports files, color console output, and JSON format. It follows a singleton pattern.