Kuali Days - Rice
Kuali Rice Introducing Kuali Core
Tadd Giles Kuali Platform Director
Tadd Giles
2
Kuali Core
13
Kuali Rice
14
Kuali Rice ❖ ❖ ❖ ❖ ❖ ❖ ❖
Kuali Enterprise Notification Kuali Enterprise Workflow Kuali Identity Management Kuali Nervous System Kuali Rapid Application Development Kuali Rules Management System Kuali Service Bus
15
Kuali Rice ❖ Two implementations ❖ Standalone ❖ Bundled ❖ Tech Platform ❖ Java ❖ MySql or Oracle ❖ JVM/Tomcat ❖ Monolithic application architecture 16
Kuali Rice ❖ Over time has become... ❖ very robust ❖ very powerful ❖ very flexible ❖ very complete
17
Kuali Rice Challenges ❖ ❖ ❖ ❖ ❖
Complex Challenge to maintain and improve Not designed for cloud Not designed for “web scale” Few RESTful web services
18
Kuali Core
19
...is heavily inspired by Rice
20
...is highly informed by Rice
21
…is not Rice 3.0
22
...is not backwards compatible
23
…is a clean start
24
...is a complete redesign
25
...is a simplification
26
…is a reimagining
27
Kuali Core
28
Design Goals ❖ ❖ ❖ ❖ ❖ ❖ ❖
Run by business users, not IT or developers Decouple from clients All functionality exposed via RESTful APIs Easy to maintain and improve Fast, reliable, scalable and secure Microservice Architecture Enable Continuous Delivery
29
Microservice Architecture 30
Monolith Architecture
Application
Database
31
Microservice Architecture
Service A
Service B
Service C
Service D
Database
Database
Database
Database
32
Continuous Delivery
33
Continuous Delivery
Commit to Master
Build and run tests
Deploy to Stage and run tests
Deploy to Production
34
Companies doing Continuous Delivery
35
Development Practices ❖ ❖ ❖ ❖ ❖ ❖
Small, incremental steps Enforce minimum of 100% test coverage Enforce coding styles Continuous delivery Daily load testing in production Constant monitoring
36
Last night’s load test
37
Monitoring for last 12 hours
38
New Tech Platform ❖ ❖ ❖ ❖
JavaScript as primary language React for web browser development Node.js for server development MongoDB for database
39
Planned Core Services ❖ ❖ ❖ ❖ ❖ ❖
Kuali Auth Kuali Users Kuali Institution Kuali Workflows Kuali Groups Kuali Forms
❖ ❖ ❖ ❖ ❖
Kuali Actions Kuali Notifications Kuali Files Kuali Discussions Kuali Rules
❖ And more…
40
Roadmap ❖ Completed ❖ v1 Auth ❖ v1 Users ❖ v1 Institution ❖ Q4 ❖ v1 Workflows ❖ v1 Groups ❖ v1 Actions
❖ Next 12 months ❖ v1 Forms ❖ v1 Notifications ❖ v1 Files ❖ v1 Discussions ❖ v1 Rules ❖ Auth: LDAP
41
Demo
42
[email protected] https://medium.com/@taddgiles
Please fill out a survey in the Guidebook app
43
Tadd Giles Kuali Platform Director
Tadd Giles
2
Kuali Core
13
Kuali Rice
14
Kuali Rice ❖ ❖ ❖ ❖ ❖ ❖ ❖
Kuali Enterprise Notification Kuali Enterprise Workflow Kuali Identity Management Kuali Nervous System Kuali Rapid Application Development Kuali Rules Management System Kuali Service Bus
15
Kuali Rice ❖ Two implementations ❖ Standalone ❖ Bundled ❖ Tech Platform ❖ Java ❖ MySql or Oracle ❖ JVM/Tomcat ❖ Monolithic application architecture 16
Kuali Rice ❖ Over time has become... ❖ very robust ❖ very powerful ❖ very flexible ❖ very complete
17
Kuali Rice Challenges ❖ ❖ ❖ ❖ ❖
Complex Challenge to maintain and improve Not designed for cloud Not designed for “web scale” Few RESTful web services
18
Kuali Core
19
...is heavily inspired by Rice
20
...is highly informed by Rice
21
…is not Rice 3.0
22
...is not backwards compatible
23
…is a clean start
24
...is a complete redesign
25
...is a simplification
26
…is a reimagining
27
Kuali Core
28
Design Goals ❖ ❖ ❖ ❖ ❖ ❖ ❖
Run by business users, not IT or developers Decouple from clients All functionality exposed via RESTful APIs Easy to maintain and improve Fast, reliable, scalable and secure Microservice Architecture Enable Continuous Delivery
29
Microservice Architecture 30
Monolith Architecture
Application
Database
31
Microservice Architecture
Service A
Service B
Service C
Service D
Database
Database
Database
Database
32
Continuous Delivery
33
Continuous Delivery
Commit to Master
Build and run tests
Deploy to Stage and run tests
Deploy to Production
34
Companies doing Continuous Delivery
35
Development Practices ❖ ❖ ❖ ❖ ❖ ❖
Small, incremental steps Enforce minimum of 100% test coverage Enforce coding styles Continuous delivery Daily load testing in production Constant monitoring
36
Last night’s load test
37
Monitoring for last 12 hours
38
New Tech Platform ❖ ❖ ❖ ❖
JavaScript as primary language React for web browser development Node.js for server development MongoDB for database
39
Planned Core Services ❖ ❖ ❖ ❖ ❖ ❖
Kuali Auth Kuali Users Kuali Institution Kuali Workflows Kuali Groups Kuali Forms
❖ ❖ ❖ ❖ ❖
Kuali Actions Kuali Notifications Kuali Files Kuali Discussions Kuali Rules
❖ And more…
40
Roadmap ❖ Completed ❖ v1 Auth ❖ v1 Users ❖ v1 Institution ❖ Q4 ❖ v1 Workflows ❖ v1 Groups ❖ v1 Actions
❖ Next 12 months ❖ v1 Forms ❖ v1 Notifications ❖ v1 Files ❖ v1 Discussions ❖ v1 Rules ❖ Auth: LDAP
41
Demo
42
[email protected] https://medium.com/@taddgiles
Please fill out a survey in the Guidebook app
43
