Webinar - how to build mobile, web and integration backends 10X faster using reactive programming. For transnational database applications generate an API in minutes, then add business rules using reactive programming. For the typical 5% of logic that remains, code the rest in server-side JavaScript.
2. Agenda
• Current situation
• Company overview
• Reactive programming & declarative development
• Turning requirements into rules
• Extending rules and events
• Q & A
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
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
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
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
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.
With that, let me pass the ball to Val Huber.
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
When state change occurs – rules are invoked.
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.