Dev(Talks): JAVA DAY2015 Java frameworks day Spring Data JPA Agenda ORM and relational mapping. Technologies Spring Data and JPA overview API usage Queries and CRUD operations Performance & speed speed APPROVED Relational data mapping JDBC Spring JDBC jOOQ QueryDSL JPA Spring Data Sergiy Morenets, 2020 ORM. Mapped entities @Getter @Setter @Entity @Table public class Product { @Id private int orders; JPA Part of J2EE (Jakarta EE) Abstracts mapping in ORM systems JPA 1.0 was introduced in May 2006 JPA 2.0 released in December 2009 JPA 2.1 released in April 2013 JPA 2.2 released in June

## +21 ## PGAS in C++: A Portable Abstraction for Distributed Data Structures ## BENJAMIN BROCK 20 21 October 24-29 ## About Me - PhD candidate at Berkeley - Advised by Kathy Yelick and Aydın Buluç 64>>(cuda::dmatrix_view(a)); ## Wrap-Up - Remote pointer types are a useful abstraction for implementing distributed data structures - Extendable to multi-GPU data structures both intra-node

## +23 ## I s std::mdspan a Zero-overhead Abstraction? ## OLEKSANDR BACHERIKOV ## I s std::mdspan a Zero-overhead Abstraction? Oleksandr Bacherikov Snap Inc ## What is std::mdspan? It's a view

Middle Tier ..... 21 2.4.1. Easier configuration of declarative transactions in XML ..... 22 2.4.2. JPA ..... 22 2.4.3. Asynchronous JMS ..... 22 2.4.4. JDBC ..... 22 2.5. The Web Tier ..... 22 2 234 12.3.5. JdoDialect ..... 235 12.4. Oracle TopLink ..... 236 12.4.1. SessionFactory abstraction ..... 236 12.4.2. TopLinkTemplate and TopLinkDaoSupport ..... 237 12.4.3. Implementing DAOs API ..... 242 12.6. JPA ..... 243 12.6.1. JPA setup in a Spring environment ..... 243 12.6.2. JpaTemplate and JpaDaoSupport ..... 248 12.6.3. Implementing DAOs based on plain JPA ..... 249 12.6.4

## Building resilient systems inside the mesh: abstraction and automation of Virtual Service generation Vladimir Georgiev, Thought Machine ## I stioCon ## Sync calls failures inside the mesh - Everyone manage Virtual Service configs. - Virtual Service configs become a release artifact. - Easy abstraction for defining timeouts and retries in a language agnostic way. - Application developers using Istio/Envoy

## PyTorch ## RNN Layer使用 主讲人：龙良曲 ## Folded model [batch, feature len]@[hidden len, feature len] $ ^{T} $ +[batch, hidden len]@[hidden len, hidden len] $ ^{T} $ [0,0,0 ... ] $$ x_{t}@w_{xh} + h_{t}@w_{hh} h0) x: [seq len, b, word vec] h0/ht: [num layers, b, h dim] out: [seq len, b, h dim] ## Single layer RNN ## ☐ ☐ ☐ rnn = nn.RNN(input_size=100, hidden_size=20, num_layers=1) print(rnn) x = torch.randn(10 h_{t}^{2}@w_{hh}^{2} $$ [0,0,0 ... ] $$ x_{t}@w_{xh}^{1} + h_{t}^{1}@w_{hh}^{1} $$ feature ## 2 layer RNN ## ☐ ☐ ☐ In [17]: rnn=nn.RNN(100, 10, num_layers=2) In [18]: rnn.__parameters.keys() Out[18]:

Default: 1 ### LSTM.forward() - out, (ht, ct) = lstm(x, [ht_1, ct_1]) x: [seq, b, vec] h/c: [num_layer, b, h] out: [seq, b, h] ## ☐ ☐ ☐ 1 lstm = nn.LSTM(input_size=100, hidden_size=20, num_layers=4) LSTMCell.forward() ■ ht, ct = lstmcell(xt, [ht_1, ct_1]) xt: [b, vec] - ht/ct: [b, h] print('one layer lstm') cell = nn.LSTMCell(input_size=100, hidden_size=20) h = torch.zeros(3, 20) c = torch shape, c.shape) torch.Size([3, 20]) torch.Size([3, 20]) ## Single layer ## ☀️ ☁️ ☁️ ## Two Layers ## ☐ ☐ ☐ print('two layer lstm') cell1 = nn.LSTMCell(input_size=100, hidden_size=30) cell2

Django documentation 1.1 Getting help 1.2 First steps 1.3 The model layer 1.4 The view layer 1.5 The template layer 1.6 Forms 1.7 The development process 1.8 The admin 1.9 Security to write reusable apps | Writing your first patch for Django ### 1.3 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application Providing initial data | Optimize database access | PostgreSQL specific features ### 1.4 The view layer Django has the concept of “views” to encapsulate the logic responsible for processing a user’s request

. . . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.7 Forms . . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application

CakePHP at a Glance • Conventions Over Configuration • The Model Layer • The View Layer • The Controller Layer • CakePHP Request Cycle • Just the Start • Additional The conventions chapter covers the various conventions that CakePHP uses. ## The Model Layer The Model layer represents the part of your application that implements the business logic. It is responsible associating or other tasks related to handling data. In the case of a social network, the Model layer would take care of tasks such as saving the user data, saving friends' associations, storing and