云中的电子商务解决方案

需积分: 10 176 浏览量更新于2024-07-23 收藏 18.73MB PDF 举报

"eCommerce in the Cloud" 本书"eCommerce in the Cloud"由Kelly Goetsch撰写，探讨了如何将电子商务解决方案迁移到云端，以利用云计算的弹性与优势。这本书主要面向有经验的和正在探索云架构的网络架构师。作者阐述了如何逐步采用公共基础设施即服务（IaaS）和平台即服务（PaaS），以便在节假日或其他特殊活动期间应对高流量。书中内容可能包括以下几个关键知识点： 1. **云基础架构**：介绍云计算的基础，包括IaaS和PaaS的概念，以及它们如何帮助电商网站灵活扩展和管理资源。IaaS提供基础硬件资源如计算、存储和网络，而PaaS则提供了运行和开发应用程序的平台。 2. **容量规划**：讨论如何根据业务需求和预期流量波动来调整云资源，确保在高峰期如节假日时能够处理大量用户访问，避免服务器过载。 3. **成本效益分析**：解释云计算的成本模型，如何根据使用情况付费，以及如何优化成本，以达到经济效益最大化。 4. **安全性与合规性**：涵盖云中的数据安全问题，包括数据加密、访问控制和合规性要求，以保护用户的隐私和商业信息。 5. **可伸缩性和弹性**：讨论云技术如何实现无缝扩展，以应对突发流量，同时在低峰期减少资源使用，保持系统稳定和高效。 6. **灾难恢复与备份**：介绍云环境下的灾难恢复策略和数据备份方案，以确保业务连续性和数据完整性。 7. **DevOps实践**：可能涵盖了DevOps文化在云环境中的应用，如何通过自动化部署、持续集成和持续交付（CI/CD）提高开发效率和产品质量。 8. **云服务提供商选择**：对比分析不同的云服务提供商，如Amazon AWS、Microsoft Azure、Google Cloud Platform等，讨论他们的特性、优势和适用场景。 9. **案例研究**：可能包含实际电商企业的云迁移案例，展示成功实施和从中获得的收益。 10. **未来趋势**：探讨电商行业的未来趋势，以及云计算如何塑造这些趋势，例如边缘计算、人工智能和物联网在电商中的应用。通过这本书，读者将能理解如何利用云计算提升电子商务的效率和用户体验，同时降低运营成本。此外，还可能学习到如何制定有效的云战略，以适应快速变化的市场环境。

www.it-ebooks.info

5. Steve Lohr, “For Impatient Web Users, an Eye Blink Is Just Too Long to Wait,” New York Times (2012), http://

nyti.ms/1esukXm

6. Greg Linden, “Make Data Useful,” Amazon.com and Findory, http://bit.ly/1k7ypZw (PowerPoint file down‐

load).

nect to a single ecommerce platform. An outage now is the equivalent of barring cus‐

tomers from entering all physical stores.

Because of increasing competition and the maturity of offerings, customers are in‐

creasingly fickle about performance. They expect response times to be instant. The New

York Times recently said: “The old two-second guideline has long been surpassed on

the racetrack of Web expectations.”

Going on further to say: “Two hundred fifty mil‐

liseconds, either slower or faster, is close to the magic number now for competitive

advantage on the Web.” Amazon.com saw a 1% increase in revenue for every 100 mil‐

liseconds of response-time improvement.

In today’s world, milliseconds matter.

Availability and performance are becoming increasingly difficult to offer as traffic has

become more prone to rapid spikes due to an increasing reliance on promotions and

marketing-driven events. We’ll discuss this more later, but it’s not uncommon to see

spikes in traffic that are one or two orders of magnitude above steady state. Social media–

based marketing can lead to campaigns going viral. From an IT administrator’s stand‐

point, the traffic can come so quickly that it looks like a distributed denial-of-service

attack, when in reality it’s likely to be a few million kids hitting refresh on their pages

in anticipation of the release of the latest hot basketball shoe.

While ecommerce has been maturing over the past two decades, the prevailing deploy‐

ment architecture looks largely as it did in the beginning—mostly static environments

fronted by web servers deployed out of a single data center. Many simply guess at what

their peaks will be and then multiply that number by five for safety. Hardware is statically

deployed and idle for most of the year. It’s been done this way for four reasons:

• IT administrators fear losing their jobs because of outages. It’s simply less risky to

throw hardware at problems.

• For a while, ecommerce deployments were small enough that the hardware cost

was negligible.

• There hasn’t been a good alternative to the static approach—cloud in its present

form didn’t exist until very recently, and it’s matured only recently.

• The old models of hosting had more accountability. If there was an outage, you

could always escalate to your vendor.

The current approach to ecommerce deployment architecture is not scalable. The rise

in traffic has ballooned environments from dozens to hundreds or even thousands of

servers. Given today’s extremely competitive business climate, it’s not feasible to have

xvi | Introduction

www.it-ebooks.info

hundreds or thousands of servers sit idle for all but a few hours out of the year. It’s also

increasingly difficult to predict traffic. Most important, and central to this book, is that

cloud computing has matured to the point where it can be used for ecommerce.

What Is Cloud?

Cloud is one of those ineffable terms that has been redefined to encompass everything,

yet means nothing. For the purposes of this book, the cloud is best characterized by

three adjectives: elastic, on demand, and metered. Let’s look at each in greater detail:

Elastic

To be considered cloud, you must be able to increase or decrease a given resource

either automatically or on demand by using self-service user interfaces or APIs. A

resource can include anything you have in your data center today—from commo‐

ditized hardware running Linux (Infrastructure-as-a-Service), to application

servers (Platform-as-a-Service), up to applications (Software-as-a-Service). The

“what” doesn’t matter all that much; it’s the fact that you can provision new

resources.

On Demand

Seeing as elastic is the first word used to describe the cloud, you must be able to

provision a resource precisely when you need it and release it when you don’t.

Metered

You should pay only for what you use. This has enormous implications, as the costs

directly reflect usage and can therefore be substantially lower.

When the term cloud is used in this book, it generally refers to public Infrastructure-

as-a-Service. We’ll spend Chapter 3 describing cloud in more detail.

Why Is the Cloud a Fit for eCommerce?

Cloud is a natural fit for ecommerce because you can provision and pay for resources

when you need them instead of building enormous static environments scaled for peaks.

The goal is to provision automatically, which we’ll discuss in Chapter 4. Without the

cloud, environments are statically built and scaled for peak load. It doesn’t make sense

when you can use a cloud. The problem of underutilization is even worse for prepro‐

duction environments, many of which are built to some scale of production yet sit even

more idle than production. Most deployments have approximately the following envi‐

ronments:

• Two production environments (each capable of handling 500% of the peak pro‐

duction traffic)

•

Three staging environments (each being 50% of production)

Introduction | xvii

www.it-ebooks.info

剩余280页未读，继续阅读

bonbonyu

粉丝: 0
资源: 7

云中的电子商务解决方案

eCommerce in the Cloud.pdf

Zhu Tao：The 'Nanotechnology' in eCommerce

Ecommerce analytics ：analyze_and_improve_the_impact_of_your_digital_strategy

Write a high converting sales focused ecommerce product description for[insert product name] With the following features

@Pointcut("execution(* com.example.ecommerce.service.OrderService.placeOrder(..))") public void placeOrder() {}

springcloud模块化开发代码的例子

帮我搭建一个商品管理,商品分类,订单信息的一个POM聚合工程

利用shell把电商数据上传到hdfs

sf有哪些模块,ec

最新资源