Hi Nitin, briefly tell us about your business.
Reasoning Global eApplications Ltd (Reasoning) is a company working in the digital commerce space. Our core business is focused around MartJack, a complete digital commerce platform that allows retailers or manufacturers to build their online stores (e-commerce websites) from scratch without requiring any IT teams or infrastructure at their end. Currently over 700 retailers/manufacturers/brands use MartJack. We are a 150+ strong team and are headquartered in Hyderabad. We also have physical presence across Mumbai, Pune, Bangalore, Chennai, Delhi, Ahemdabad and Jaipur apart from catering to requirements from all across India through our in-bound channels.
How have you incorporated Amazon Web Services (AWS) as part of your architecture?
MartJack is a Software as a Service offering and is a completely hosted solution. AWS is the foundation of our infrastructure on top of which we have our custom infrastructure architecture. We use EC2, S3, Cloudwatch, Backups (Snapshots) among other services.
Please describe what you were using for your infrastructure prior to using AWS technology.
We were hosted on a local datacenter before moving to AWS. We are a 100% AWS hosted platform as of today.
Why did you decide to use AWS?
Three main reasons made us switch to AWS – scalability, reliability and manageability. AWS allows us to scale fast while being able to provide a high uptime SLA to our clients. Both in-instance scale up as well as scale out to multiple instances allows us to easily scale our infrastructure to meet the needs of our fast growing business. Moreover, the security capabilities in AWS have allowed us to have a clean chit in terms of attacks so far.
How has AWS helped your business?
Our costs have come down to around 50% of what we were incurring earlier on a per-customer basis. Currently we run around 30 instances and serve around 10 million consumers on MartJack powered websites every month.
Have you learned any valuable lessons during the AWS development process that you’d like to pass on?
Mainly about understanding that AWS is a very scalable datacenter on a cloud with capabilities for both in-instance scale up as well as scale out to multiple instances. So one needs to build their architecture keeping this in mind to help ensure low cost of incremental scale up or scale out as they grow. We have achieved this by breaking down our entire infrastructure into niche-dedicated server roles so that a given requirements or situation requires scale up of just 1 or 2 of the roles instead of a blind mammoth scale up. This allows us to get the maximum benefit in terms of cost/scalability on AWS.
Do you have any future plans to incorporate other AWS solutions?
As of now we are considering using RDS, CDN and multi-location deployments in AWS but all of these are at an assessment stage right now
Is there anything else you would like to share?
Just that we are very happy about our choice i.e. AWS for our base infrastructure. We are looking forward to some new features in terms of robustness, RDS clustering etc. to further strengthen our capabilities with AWS
AWS allows us as a platform business to take care of two of our most critical requirements – first, the ability to scale the capabilities for a given client according to their needs including marketing spikes etc. and second, the ability to scale our entire infrastructure seamlessly as we continue to grow our client base to help ensure a high quality of service to our clients.
AWS is the foundation of our infrastructure on top of which we have our custom infrastructure architecture. We use EC2, S3, Cloudwatch, Backups (Snapshots) among other services
To learn more, visit http://ereasoning.com/.
Added February 7, 2012