Loading...
Answers
MenuSAAS - What basic server architecture should we go for?
Answers
I think you're not fully embracing the lean startup methodology.
Is your SaaS handling some operations that are a matter of life and death or critical mission thing for an organization?
if the answer is No start with simplest option and do a soft launch and invite some carefully selected (50) beta testers.
Get the service going and gather feedback as much as possible. Then when you're at version 1.5 or 2.0 you'd know the problem you're solving a lot better.
Slavi,
Orbisius & qSandbox
PaaS is probably your best bet if you want to avoid hiring someone to manage things. Even managing two servers can eat up huge portions of your time — especially if these are new waters for you.
PHP/MySQL put you at a little bit of a risk, performance-wise, so be sure to keep an eye on resource usage.
In my current role, I'm putting WordPress sites up against thousands of concurrent users, so while the exact usage probably isn't the same, the tech stack is similar.
I'd probably do something like this (pretty much what I use): a Rackspace setup that can automatically scale when traffic spikes, with New Relic to keep an eye on performance and leaks in the app itself, and probably nginx/Varnish to try and keep the load off the servers in the first place (assuming any part of your app is cacheable).
A stack like that is not cheap compared to free, but it's cheap compared to a full-time ops engineer or spending a Friday/Saturday night trying to self-diagnose bottlenecks.
Good luck!
Take a look at Google Compute Engine. You'll pay by the drink, metered on your resource usage. Infrastructure cost drop drastically and you'll be on "GOOGLE's" gear / cloud. As an example, take a look at GetCloudCenter.com - the portal is running on GCE using LAMp servers, PHP, not sure about the DB side of things. They offer a demo portal to spin up and sell DaaS. Best of luck!
Clarity about the requirements of the service design should inform how you select the best platform deployment model now and in the future.
The Service Design should encompass 1) Availability Requirements, 2) Performance Requirements and 3) Scalability Requirements. Availability Requirements can be expressed in terms of acceptable number of downtime hours per year, Performance Requirements can be expressed in terms of maximum required transactions per second, and Scalability can be expressed in terms of the degree of linearity in adding additional peal transactional capacity to the system.
Implementing these service design requirements using a PAAS approach will require having significant technical expertise on staff. A different and more flexible option to consider would be to use an infrastructure-on-demand approach as currently being offered by Amazon Web Services (AWS).
AWS would allow you to deploy your preferred technology stack at an initially smaller cost commitment level and then scale up both the transactional capacity and redundancy as the build out of your business model warrants.
Related Questions
-
How should we plan a well-executed SaaS product launch to an existing customer base?
I'm a product developer, startup veteran, and advisor to SaaS companies. Hopefully you've been already developing this new product with input from your existing customers, letting them beta test it and give feedback. (If not, my advice is to STOP immediately and get enough pilot customers involved to be sure that you're delivering something really valuable to them, that works the way they expect it to work, is easy to understand and get started with, etc.. The last thing you want is to do a big splashy launch of a product that is D.O.A. because you built what you assumed the customers wanted instead of they actually demonstrated that they wanted.) OK, so let's assume that you've got customers in the loop. Interview the heck out of them. Really understand how they use the product, why they use the product, what makes it valuable to them, what they can do with it that they couldn't do before, etc. If the product's not done enough for them to be best testing it yet and getting results, at least get some insights into how they see themselves getting results from it. How does it/will it change their lives? As you do this, be on the lookout for things that really resonate. Emotional language, for example. "It's such a relief that I don't have to worry about sending invoices manually anymore." (or whatever pain it is that your software solves) Also look for (and try to elicit) specific result statements: "This new software saves me [or is going to save me] 15 hours a week. Now I can spend that time where I really want to, with my kids ( ... my cat ... my golf buddies ... )" You're doing this for three reasons: 1) This stuff makes for phenomenal testimonials; 2) it helps you come up with great ideas for pre-launch content; and 3) it generates *PURE SOLD GOLD* you'll use in writing the copy for your launch offer. OK, launch mechanics. There are people who teach huge long expensive courses on this stuff. I'll give you the Cliff's notes. While I haven't personally run a major product launch, I have been trained in the strategy and am very familiar with it. - Plan your launch period in advance. You might want to do a pre-launch sequence that lasts 1, 2, even 3 months depending on the magnitude of your product and how much effort you're willing to put into creating content for the launch. - Create some teaser content of interest to your customers who might want to buy this product. Offer to teach them something, or offer to give them a sneak-peak behind-the-scenes of your new product. - Send an enticing offer for this content out to your list. Get people who are interested in this content to sign up for it. This creates your launch email list. - Send your launch list weekly updates: development milestones, sneak-peak screenshots, videos, educational material, interviews with/testimonials from beta users, and so on. - You're not trying to sell here yet (not hard sell at least). Drop some hints that there is going to be a special offer when the product launches, just for special loyal customers like them. - Create at least three videos on topics that are really, really interesting to your prospective customers... not necessarily about your new product itself, but teach them about what they can achieve with it, or what others have achieved with it already. As you publish these videos, send the link out to your launch list. - Also send out an offer to see these videos to your main list, to entice more people to sign up for your launch list. - As you get closer to launch time, keep sending frequent updates to the pre-launch list, and send another email out to your main list to let them know that the product is launching soon, and that if they're interested in the special one-time-only launch pricing, they need to sign up for the "early bird list" (your launch list). - Send out a 24-hour notice that the launch is going to happen soon, and the launch pricing will only be available for a limited time (potentially, to a limited number of customers ... to increase scarcity and urgency). - I recommend that even if you plan to open the product up to all your customers that at launch time you limit it to a smaller number. This makes the inevitable post-launch gremlins less painful to deal with because you have fewer customers, and it motivates people to buy because they fear that they'll lose the opportunity to do so. You can open the product up to more people later... the delay will result in pent-up demand and easier sales. - Start the launch. Tell your early-bird launch list a few hours early, then tell your main list. Direct them to a web page with a video and long-form sales copy of your launch offer. - Send out 2-day, 1-day, 12-hour, etc. notices that the launch is ending soon and reminding people what they're missing out on if they don't act now. If you're offering a limited number of spots, tell people what percentage has already sold out. Remind people that if they're "on the fence" about this, that this is the time to make a decision. - Send out an email letting people know that the launch is over and thanking them for their support and their vote of confidence. Tell the people who didn't buy (or didn't get in) that you'll let them know that the product will be opening up for new registrations some time in the future. (You may get people sending you emails begging to be let in at this point, if your product is desirable and your marketing was executed well.) And, of course, you don't just have to promote your launch content to your existing customer list ... you can post it to social media (and encourage your customers to do so) to attract brand new customers into your world. If you'd like to go into more detail about launch planning for your specific product and market, I'd be happy to jump on a call and talk about ways to make this work for you.BB
-
What is the best tutorial to get started with CakePHP?
I would probably look at a course on udemy for that specific case https://www.udemy.com/getting-started-with-php-programming/?dtcode=MzjhAx31ASRHHJ
-
For a SaaS, I find that Stripe is not available to Indian companies. What are other Stripe-like payment gateway options for Indian companies?
there is Balanced, Dwolla, Braintree but none of them seem to work in India yet.HJ
-
How important is coding knowledge in starting a SAAS business? Should I start by learning code or just get started on the idea? Book suggestions?
I started a large SaaS Company for B2B where perfection in code is as importante as it gets. So here is my advice, DON'T CODE until you know what the Saas Really is. First start understanding what the problem REALLY is. Interview people and actually spend 100% of your time doing Customer Discovery. (This sounds easy but it is a skill you'll have to develop far more important than coding). Once you understand what the problem is, come up with a value proposition. Still no code. Then make a sell. If you can actually find things already existing that you can Hack and put it together then use that. Then make another sell. If you can sell it to at least 50 people if you are B2C, or if you are B2B you should have at least 1 customer. Once you do that then start automating some parts of the solution that you have hacked and so on. But THE most important thing is to be in constant conversations with your customers and hot leads. Remember you are a customer making machine not a coding machine, the first one is where the money is. Hope this helped you, if you want to talk more about customer discovery and customer development, just give me a call.JC
-
How to upload images to a server in titanium? I have a php script in the server that receives the images, but it's not working: can't upload images.
you should rather put this question on stackoverflow.com, catch the error message, paste your code so experts can understand what's going wrong. Example : http://stackoverflow.com/questions/2532478/how-to-upload-images-from-iphone-app-developed-using-titaniumLR
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.