wuming.net
域名年龄: 24年4个月20天HTTP/1.1 200 OK 类型:text/html; charset=UTF-8 过期时间:2016年11月14日 23:56:59 访问时间:2016年11月14日 23:56:59 缓存控制:private, max-age=0 修改日期:2016年07月31日 04:44:16 网页标记:W/"fef8274917e415aa782491e4fca720bee0eb21d66bfeaea3af275037606924b6" Content-Encoding: gzip X-Content-Type-Options: nosniff 网站XSS保护:1; mode=block 文件大小:23883 服务器:GSE 网站编码:UTF-8
wuming zhangmy personal blog about IT Infrastructure and Operations & life thoughts...Saturday, July 30, 2016Choosing CDNCDN stands for Content Delivery Network, do you need it? Well, let's see.1. Are you running a high traffic volume website and your users are distributed? Y/N2. Is latency important for your users? Y/NIf you answer yes on both, then you should use CDN. Here is a list of items you should consider when choose a CDNShield your originSpeed of purge cacheAPI support on normal use and configurationOverride path and cache behaviorsupport multiple originGeoIP and conditional based rewriteWAFLogfile stream to S3 or other servicesadmin support multi factor authenticationHTTP 2.0Customer support (yes, you will need it)apex domain supportDeploy new config speed3rd party integrationIgnore query paramatersCommunityI'm a long time CDN user, including some market leading vendors. Recently a migration to Fastly (varnish based solution) showed smaller players are not necessary slower.To all friends out there, bias-free. Try out and see what's best for you!Posted bywumingat10:44 PMNo comments:Saturday, September 26, 2015Victim of its own successWednesday this week, I believe four different people from different companies and departments told me that they are victim of their own successes. Coincident? Maybe, maybe not. It had me thinking over for few days now, why and how to avoid it?I did some research and trying to understand what does it mean? Those companies have in common growth pain, being successful in business areas also lead to to debt in other area. Another common denominator is IT and cloud centric, as a part of problem or the solution.Many companies suffer from unpredicted IT complexity. Systems and integrations tend to be function focused. Creative developers and system integrators can come up some really “wow or wtf” solutions. Some people believe documentation is the best solution. I believe focus on simplify the complicity and make system standard or KISS. Most of us are not that special snowflake and all those special variants won’t add up in the end. Imagine services are interconnected to each other to complete a business activity. Every one-off hack/deviant will increase fail rate for your next business changes.IT landscape is like your home. It needs maintain and housekeeping. When your business is going strong, you might just purchases new furnitures/systems or maybe even a new house to satisfy your need. How ever your walls, water pipes and kitchen drain are like infrastructure services and should always work. You might drop your cloth / data here and there, but sooner or later, someone has to organize it. Finding the balance between housekeeping and growth is not always trivial. I'd rather do regular small/medium housekeeping than some serious renovation. This includes keep a right amount of tech debt. Risk assessment can help the organization to find how they are doing.Last not least is people struggle
© 2010 - 2020 网站综合信息查询 同IP网站查询 相关类似网站查询 网站备案查询网站地图 最新查询 最近更新 优秀网站 热门网站 全部网站 同IP查询 备案查询
2025-06-20 02:22, Process in 0.0095 second.