Показ дописів із міткою SaaS. Показати всі дописи
Показ дописів із міткою SaaS. Показати всі дописи
понеділок, 15 квітня 2013 р.
Continuous delivery
I would like share latest presentation about Continuous delivery. This cover most common bussines scenarious where CD can help and metodologies which supports SDLC.
понеділок, 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
вівторок, 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.
понеділок, 25 квітня 2011 р.
10 main requirements for SaaS/Cloud applications
Find interesting post regarding 10 main requirements for SaaS/Cloud applications. Below is short notes:
1. True Multi-tenancy. Multi-tenancy is the only proven SaaS delivery architecture that eliminates many of the problems created by the traditional software licensing and upgrade model—period.
2. Regularly Delivered, Vendor-Managed Updates. A cloud application is a single version of software that is regularly updated, often several times a year, for all customers, at no additional charge.
3. Seamless Integration On Demand. Cloud applications should be built from the ground up to lower the cost, time, and risk of integrating them with existing on-premise and on-demand applications.
4. Business-Driven Configurability. Cloud apps should be configurable, so your IT organization is freed from costly customizations (the most over-rated virtue of traditional software, in my opinion), and businesspeople can configure processes that meet the specific needs of the organization. That said, you should be able to choose from among multiple types of configurations.
5. World-Class Data Center and Security. A cloud application provider should be able to offer world-class security and data privacy better than its customers can do on their own, and at no additional cost. That includes physical, network, application, and data-level security, as well as full back-up and disaster recovery. The provider should be compliant with security-oriented laws and auditing programs, including Safe Harbor, ISO 27001, and SAS70 Type II.
6. A High-Performance, Sustainable IT Infrastructure. The provider should maintain a high-performance IT infrastructure, which includes the data centers and databases, operating systems, networks, and storage systems used to run cloud applications and manage customer data.
7. Predictable Total Cost of Ownership Model. There should be no surprise costs with cloud applications. Implementation costs should be predictable, subscription-based pricing should have no hidden fees, and no investments should be required for hardware and software license fees.
8. Faster Deployment. Since cloud applications don’t require investments and installation of hardware and software, you should be able to get them running and productive in a fraction of the time compared with on-premise software.
9. Control. Cloud applications should allow you complete control of your organization’s data, even though it is located off premise. Nothing should hinder your ability to import, export, purge, and archive data to and from the application without having to first contact the SaaS vendor.
10. Liberation from Non-Strategic IT Issues. Cloud applications should free teams from time and energy spent on non-strategic, back-office IT operations and software coding. Today and into the future, the most highly valued CIOs—the ones that become heroes to the business—are those who are closely aligned with strategic business initiatives and drive the IT projects that support those initiatives.
Original post is here
1. True Multi-tenancy. Multi-tenancy is the only proven SaaS delivery architecture that eliminates many of the problems created by the traditional software licensing and upgrade model—period.
2. Regularly Delivered, Vendor-Managed Updates. A cloud application is a single version of software that is regularly updated, often several times a year, for all customers, at no additional charge.
3. Seamless Integration On Demand. Cloud applications should be built from the ground up to lower the cost, time, and risk of integrating them with existing on-premise and on-demand applications.
4. Business-Driven Configurability. Cloud apps should be configurable, so your IT organization is freed from costly customizations (the most over-rated virtue of traditional software, in my opinion), and businesspeople can configure processes that meet the specific needs of the organization. That said, you should be able to choose from among multiple types of configurations.
5. World-Class Data Center and Security. A cloud application provider should be able to offer world-class security and data privacy better than its customers can do on their own, and at no additional cost. That includes physical, network, application, and data-level security, as well as full back-up and disaster recovery. The provider should be compliant with security-oriented laws and auditing programs, including Safe Harbor, ISO 27001, and SAS70 Type II.
6. A High-Performance, Sustainable IT Infrastructure. The provider should maintain a high-performance IT infrastructure, which includes the data centers and databases, operating systems, networks, and storage systems used to run cloud applications and manage customer data.
7. Predictable Total Cost of Ownership Model. There should be no surprise costs with cloud applications. Implementation costs should be predictable, subscription-based pricing should have no hidden fees, and no investments should be required for hardware and software license fees.
8. Faster Deployment. Since cloud applications don’t require investments and installation of hardware and software, you should be able to get them running and productive in a fraction of the time compared with on-premise software.
9. Control. Cloud applications should allow you complete control of your organization’s data, even though it is located off premise. Nothing should hinder your ability to import, export, purge, and archive data to and from the application without having to first contact the SaaS vendor.
10. Liberation from Non-Strategic IT Issues. Cloud applications should free teams from time and energy spent on non-strategic, back-office IT operations and software coding. Today and into the future, the most highly valued CIOs—the ones that become heroes to the business—are those who are closely aligned with strategic business initiatives and drive the IT projects that support those initiatives.
Original post is here
Підписатися на:
Дописи (Atom)