субота, 17 березня 2012 р.
Tablets market
Just noticed interesting fact in the some overview about Tablet marked share based on the latest results from 2011
The full story is available here
понеділок, 28 листопада 2011 р.
понеділок, 21 листопада 2011 р.
Hosting
Last week I noticed a lot of posts regarding pricing for Cloud hosting. Most of the authors states that this approach is more expensive in (1,5 - 5) times. As per me it’s reasonable since using virtualization means that hardware is shared and performance is less in comparison with managed hosting and private datacenter.
Here is my thoughts what hosting should be used and for what reasons:
1. Cloud – mostly applicable for startups. Low price for upfront investment, ability grow very quickly since adding new virtual machines are very easy thru API interface. Hosting expenses has less priority than getting more customers in short period of time.
2. Private Data-centers – Applicable for the solution if your operation team has experience for hosting similar SaaS products, Ops processes are established and you have clear vision how new system will be operated and loaded.
3. Managed Hosting – Same as above except – no huge upfront investment for hardware. Please note that managed hosting monitoring will cover monitoring of servers availability and does not cover application and services availability
As a conclusion – please select type of hosting carefully and take in to consideration whole Pros and Cons for your solution and look for one or two steps ahead in the future. Because you may lose a little now but get huge benefit in the future …
Here is my thoughts what hosting should be used and for what reasons:
1. Cloud – mostly applicable for startups. Low price for upfront investment, ability grow very quickly since adding new virtual machines are very easy thru API interface. Hosting expenses has less priority than getting more customers in short period of time.
2. Private Data-centers – Applicable for the solution if your operation team has experience for hosting similar SaaS products, Ops processes are established and you have clear vision how new system will be operated and loaded.
3. Managed Hosting – Same as above except – no huge upfront investment for hardware. Please note that managed hosting monitoring will cover monitoring of servers availability and does not cover application and services availability
As a conclusion – please select type of hosting carefully and take in to consideration whole Pros and Cons for your solution and look for one or two steps ahead in the future. Because you may lose a little now but get huge benefit in the future …
четвер, 17 листопада 2011 р.
Most large-scale web sites technology map
I've found interesting post where author summarize technologies used for most large-scale web sites
вівторок, 1 листопада 2011 р.
Utah SaaS Workshop (Update)
As I promised, in this post I am publishing some materials about Utah workshop. Follow the link you could collect general information about workshop and see presentation what Russ provide. In additional to this I would like share some overview:
1. Personal communication is more valuable and help talk about details and suggest better approaches than general questions what come up during presentation and panel session
2. DB is the major paint for every one
3. Sometime even simple idea what is lay on top may be useful for clients
4. Abstract presentation may not be attractive for the participants – next time we may concentrate on the discussion solution for different problem solving from technical stand point and business impact.
5. Grate event :) and cool participants :):)
1. Personal communication is more valuable and help talk about details and suggest better approaches than general questions what come up during presentation and panel session
2. DB is the major paint for every one
3. Sometime even simple idea what is lay on top may be useful for clients
4. Abstract presentation may not be attractive for the participants – next time we may concentrate on the discussion solution for different problem solving from technical stand point and business impact.
5. Grate event :) and cool participants :):)
вівторок, 18 жовтня 2011 р.
Utah SaaS Workshop
This Tuesday, I’ve performing the Q&A session in SoftServe SaaS workshop in Utah. It was the first time when I was as front man and answer on questions related to the SaaS architecture and solutions. Good experience for me, meet new interesting people and of course observe what is an interest of the audience. I will post more details later but as a short summary – it was grate day and we (me, Serge – Director of Architecture Group and Russ – VP of SaaS) successfully hold this event.
середа, 27 квітня 2011 р.
Main reasons for Choosing Scale-Out
1. Continuous Availability/Redundancy: You should assume that failure is inevitable, and therefore having one big system is going to lead to a single point of failure. In addition, the recovery process is going to be fairly long which could lead to a extended down-time.
2. Cost/Performance Flexibility: As hardware costs and capacity tend to vary quickly over time, you want to have the flexibility to choose the optimal configuration setup at any given time or opportunity to optimize cost/performance. If your system is designed for scale-up only, then you are pretty much locked into a certain minimum price driven by the hardware that you are using. This could be even more relevant if you are an ISV or SaaS provider, where the cost margin of your application is critical to your business. In a competitive situation, the lack of flexibility could actually kill your business.
3. Continuous Upgrades: Building an application as one big unit is going to make it harder or even impossible to add or change pieces of code individually, without bringing the entire system down. In these cases it is probably better to decouple your application into concrete sets of services that can be maintained independently.
4. Geographical Distribution: There are cases where an application needs to be spread across data centers or geographical location to handle disaster recovery scenarios or to reduce geographical latency. In these cases you are forced to distribute your application and the option of putting it in a single box doesn’t exist.
2. Cost/Performance Flexibility: As hardware costs and capacity tend to vary quickly over time, you want to have the flexibility to choose the optimal configuration setup at any given time or opportunity to optimize cost/performance. If your system is designed for scale-up only, then you are pretty much locked into a certain minimum price driven by the hardware that you are using. This could be even more relevant if you are an ISV or SaaS provider, where the cost margin of your application is critical to your business. In a competitive situation, the lack of flexibility could actually kill your business.
3. Continuous Upgrades: Building an application as one big unit is going to make it harder or even impossible to add or change pieces of code individually, without bringing the entire system down. In these cases it is probably better to decouple your application into concrete sets of services that can be maintained independently.
4. Geographical Distribution: There are cases where an application needs to be spread across data centers or geographical location to handle disaster recovery scenarios or to reduce geographical latency. In these cases you are forced to distribute your application and the option of putting it in a single box doesn’t exist.
Підписатися на:
Дописи (Atom)