From Specs To App 10X Faster Using Reactive Programming
- 1. Espresso Logic From Specs To App 10X Faster Using Reactive Programming
- 2. Agenda • Current situation • Company overview • Reactive programming & declarative development • Turning requirements into rules • Extending rules and events • Q & A
- 3. Current Situation Business Application Requirements Application Running in Production
- 4. With Reactive Programming Business Application Requirements Application Running in Production balance < credit_limit balance = sum (unpaid orders.amount_total) amount_total = sum (lineitem amount) amount = product_price * qty_ordered product_price = copy(product.price)
- 7. Declarative Development • More productive – closer to the business • Move away from converting requirements into code
- 8. Declarative Reactive Programming subscribe() handleEvent() Declare Expression Watch React JavaRX Observer Espresso Angular Spreadsheet
- 9. Espresso Business Rules • Rules applied to business entities and attributes – Derivations – Validations – Events - extensibility
- 10. Rules Improve Application Quality Aligning IT and the business • Guaranteed Re-use • Validate requirements • Business users can read and understand rules • Rules bridge users and IT
- 11. Validation
- 12. Derivation – Sum
- 13. Derivation – Formula (JavaScript)
- 15. Solves these Use Cases… Add Order Delete Order Add Detail Delete Detail Change Detail Qty Reselect Product …. Balance < CreditLimit Balance = sum (Orders.AmountTotal) AmountTotal = sum (Lineitem Amount) Amount = UnitPrice * Quantity 1 UnitPrice = copy(UnitPrice) 1 2 2 3 3 4 4 10X Faster? Seriously.
- 16. Espresso Metrics • Rules cover 95+% of complex business cases •40X expressive power Approach Metrics Java 480 Triggers 220 Logic 5
- 17. Rules + JavaScript Events for the last 5%
- 18. Business Agility – Maintenance is Key • Avoid the archaeology of maintenance • Just change rules – Re-ordered – Re-optimized
- 19. Challenges to Address Complexity • Performance – Single row adjustments – Pruning • Transparency – Rule logging / trace – Debugger
- 20. Demo
- 21. Summary • With Espresso reactive programming you can – Reduce Time to Market – Accelerate maintenance – Improve application quality
- 22. Next Step PROOF Work with Espresso to arrange a charge proof-of-concept with your data No charge
- 23. Q & A Business: ron@espressologic.com Technical: tyler@espressologic.com val@espressologic.com www.espressologic.com 844-463-7773
Editor's Notes
- #2: Welcome to the Espresso Logic webinar series. My name is Ron Kaplan and I’ll be your host for this session. This webinar will describe a new and better way to build applications using reactive programming. If you have any questions during the session, please put them in the question window in the GoToMeeting widget. We will answer them at the end of the presentation
- #3: This is the agenda for our 30-minute session. Let me introduce our speakers this morning. Val Huber is a cofounder, and Espresso's CTO. He has decades of experience in the business as CTO. Hr is the visionary behind the technology you will see today. Tyler band is our Customer Advisory Engineer at Espresso Logic. Tyler's been in the industry for more than 20 years leading the development of large projects. During his career, he has managed development efforts at companies such as Marriott, Cendant, Fidelity and J.P. Morgan - some with over 100 people. I am going to position the session then pass control to our presenters
- #4: The pace of business is increasing. When customers ask for new applications, they need them yesterday. When they ask for change they need it tomorrow. And when you deliver an update, it is not what they wanted This pace that putting immense pressure on the development organization. It's typical for an end-user to demand an application where they have only a fuzzy understanding of the requirements – and yet they need it ASAP Adding to the pressure are initiatives such as BYOD – bring your own mobile device, We see developers building applications that focus on getting the functionality right, but sometimes result in poor performing applications. They might start working on the client application, putting the business logic behind the button – logic that belongs on the server. The result is a bad architecture with poor performance. What we need is a better way to build applications. We think that way is using declarative development and reactive programming
- #5: Espresso technology enables IT to collaborate with business users to come up with a precise set of business requirements for applications. Using espresso, customers QUICKLY make those requirements executable. Together, IT and the business, work through a set of default screens with WORKING logic to validate the requirements. If there is a problem, developers make quick changes to the requirements, and they iterate again - streamlining the development process and ensuring the business gets what it needs.
- #6: With that, let me pass the ball to Val Huber.
- #7: Executable business requirements Scalable runtime platform - in cloud or on premise Database access and processing RESTful API & fine-grained security On AWS or Azure or VMWare
- #10: When state change occurs – rules are invoked.
- #22: Espresso technology enables IT to collaborate with business users to come up with a precise set of business requirements for applications. Using espresso, customers QUICKLY make those requirements executable. Together, IT and the business, work through a set of default screens with WORKING logic to validate the requirements. If there is a problem, developers make quick changes to the requirements, and they iterate again - streamlining the development process and ensuring the business gets what it needs.