SIIA is delighted to welcome our newest member Asteor Software. I had a chance to sit down with Shankar Krishnamoorthy to learn more about their application development platform.

Rhianna: Welcome to SIIA. Tell me a little bit about Techcello and what makes your solutions unique.

Shankar: Techcello is a cloud ready, multi-tenant application development platform – used by ISVs and Enterprises to build their products and applications faster and better.  We are featured as Gartner Cool Vendor and Nasscom Emerge League of 10 company.   ISVs who are looking at building green-field SaaS products or migrating their existing on-premise products to SaaS look at using Techcello as the platform for building their SaaS products.  And, large enterprises use our Techcello platform to build their applications such as dealership management system, benefits management systems, etc. because of our strong security engine, tenant hierarchy capabilities, business rules & workflow features, developer productivity  components, etc.  Invision, Secova, Duosoft, Roferez, Sutherland Global Services are some of our prestigious customers who have used Techcello extensively for building their applications.

Approach to application development on top of .NET is unique in Techcello.  We have productized the complex portions of building software (architecture, plumbing, data security, etc.) into Techcello and let the developers focus on building their business specific functionalities rather than bogged down by engineering complexities.  They consume the API/Webservices provided by Techcello for these complex functionalities.  While developers will stay with their usual development style and approach for building the software, it will be governed by Techcello so that complexities are taken care by Techcello and also the developers are lot more productive.  This saves anywhere between 90 to 150 people months of effort in application development on a typical large project.   So, time to market is faster.  Apart from saving cost and effort, the fact that our customers use .NET technology, which gives them the complete control and flexibility in their technical approach/decisions. We believe this provides a very unique advantage for Techcello.

Rhianna: This past year you conducted a survey on SaaS/Cloud Multi-Tenancy. Can you tell us a little about your findings?

Shankar: We asked ISVs “Where are you on the road to Cloud, SaaS and Multi-tenancy”.  We mapped Cloud adoption (Current and Planned), SaaS adoption (Current and Planned), Multi-tenancy adoption (Current and Planned), Development Approaches and Platforms. The responses show that there is a positive trend across the industry towards Cloud, SaaS and Multi-tenancy in that order.  Most companies understand the challenges, skills and investments required to build Configurable, Multi-tenant applications for a scalable Private or Public Cloud.  They recognize that shifting to SaaS requires different kind of approaches both towards software development and operationalization.  And, they prefer to stick with 3GL platforms such as.NET and J2EE for such development.   This is more towards getting freedom, flexibility and talent.  The results can be viewed here : http://blog.techcello.com/2012/04/cloud-saas-multi-tenancy-techcello-survey-2012/

Rhianna: What are some of the biggest challenges that companies face when engineering a Multi-tenant SaaS application?

Major challenge is the need of understanding multi-tenancy holistically.  Each tenant data has to be secured at all levels – whether it is user data, business rules, workflow, extension fields, etc.  Application architecture has to be built on top of data security considerations.  This also leads to several non-functional requirements.  People often underestimate the effort here. Overheads can be as high as 30%.  For example, Multi-tenant SaaS implies a single code base for 1000s of customers.  That brings in a lot of other implied needs such as the ability to customize the data models, views, rules and workflows at the end user / tenant level.  The set-up as well as enforcement of “Who sees / does what” in the system, should also be dynamically managed during run time as it may vary depending on the region / vertical / customer. Many products are designed for global use and hence we need a layered hierarchy of tenants and users.  Add to these, the obvious challenges of performance and scalability on the Cloud.   Building all these capabilities is not rocket science.  But the expertise and experience required is not easy to find; plus, it consumes good amount of time.  Developers often prefer to focus on the business functionalities and rightfully so.  But it is too risky to leave these critical engineering aspects to be closely coupled with business features.  Even for customers who want to build the whole stack ground up, we always recommend that they create a separate framework team internally to build and maintain the engineering stack.

We have written an ebook on Simplifying multi-tenant application development and it is available for you to download from our website, www.techcello.com.  We have covered all aspects of engineering a multi-tenant application development and it has received rave reviews from some of the readers/customers.

Rhianna: I saw a white paper you published on Non-Functional Requirements (NFRs). How do you define the NFRs and why is it critical to do so?

Shankar: Non-functional requirements are something which you may not define explicitly in your product specifications, but, expect that the product should have these.  Performance, Security, Scalability, Configurability, etc. will generally come under NFR as these are not generally spelt out explicitly.  If the NFRs of a custom .NET solution built for a specific customer consumes 10-15% of overall effort, the NFRs of multi-tenant SaaS products could take as high as 30%.  If the product does not meet NFRs expected by a customer, it can lead to several issues (eg. Unsatisfactory performance of the software, unsatisfied customers, revenue loss, etc.).  Thinking about them in the form of a productized framework (whether it is built in house or bought from outside), is critical for the long term TCO and maintainability.   Many people have gone to the market with Multi-tenant products thinking that it is nothing more than adding tenant ID to the database tables. And they often have to re-engineer / re-build as they go along or compromise on their competitive advantage. CEOs and CTOs should take an active role in evaluating the NFR Check list.  Based on the positive feedback we got for our white paper, we have now built an excel sheet that helps CEOs and CTOs think and choose what NFRs are needed now and in the future and calculate the effort and money that needs to be invested on them.  Please write to info@techcello.com to get more details on this ROI calculator.

Rhianna Collier is VP for the Software Division at SIIA.