Let's consider an Integrator, perhaps using with a framework that has been successfully deployed in the past, and pose the question: does it make sense to adopt Espresso Logic?
The first question is the business model. If it is to maximize billing of attractive rates, then Espresso Logic might not fit into your plans. But, if your business model is based on delivering value, and fostering a long-term customer relationship, then Espresso Logic is well worth considering as described below.
Partners who close and support business should be able to share the recurrent revenue stream implicit in offerring business logic as a service. So, in addition to revenue from delivering great apps, you can share in value provided as the application is used.
Please contact us to discuss.
With Espresso Logic, over 95% of your business logic is expressed in annotations, each of which represents around 100 lines of code.
This adds up fast:
A typical Domain Object may require 1,000 lines of code. Let's presume there are 100 such objects: 100k lines of code. If a developer can deliver 50 lines of code / day (most estimates are more like 12-25), this represents 2,000 days of work, or about 10 staff years.
Studies have suggested that a line of code requires the same amount of time, independent of language. Since a rule represents 100 lines of code, our code base is 1k lines - 20 days of work
These reduced costs can be shared with your client. That means you can deliver at lower cost, with extremely competitive pricing.
In addition to raw cost savings, you also deliver substantially enhanced value, as discussed below.
Offering a less expensive solution is always attractive, but perhaps even more important is delivering significantly better results for your client, both instantly and over the life time of the project.
Delivering a significantly better result - in ways that are clear and demonstrable - can lead to landing more business, and more repeat business.
Winning the business often requires a prototype. Our partners tell us that, using conventional approaches, a prototype typically requires 2 weeks for the client, and 2 weeks for the server. Using Espresso, the server prototype is reduced to hours, so they are able to show prospects real results in half the time.
It is well known that the bulk of costs are in maintenance. Automatic Ordering means you do not have to spend huge amounts of time unravelling the ordering of existing code - you simply alter the logic as required, the dependency management ensures proper execution order. Similarly, automatic optimization means that the execution speed does not degrade as it does in manual systems where optimizations are deferred due to time pressures.
Architects responsible for acquired systems need to understand how they work. 100k lines of code is inevitably written by many individuals over an extended period of time. Given the complexities of multi-table logic (service layer? Data Access Objects?), architecture quality is likely to be uneven.
Better margins and results are good, but only if they are delivered. It is no secret that many implementations fail, even when starting with an existing framework.
Business Logic Automation can reduce risk:
A significant cost of failure is requirements risk: misunderstood or undiscovered requirements. Logic transparency can reduce misunderstandings, and Logicdoc makes clear exactly what is delivered.
Integration testing is a key point of failure, where every test reveals more bugs. These are often due to lack of re-use - the system applied the required logic in Use Case 1, but it was overlooked in Use Case 2.