Skip to main content

Akamai user conference

Had a good time in Miami for a few days this week, got a lot of good content from the conference. I'm going to go over my notes some more next week, but there are some of the highlights from the show:

New offering
Fraud detection and scoring - Akamai does tokenization removing PCI scope, and they can build a profile on the end users and given them scores.

Cybersource - they are one of the processors of the akamai pci solution.

Edge encryption - Encrypts the data at the edge all the way to the database Only privledged systems can decrypt the data from the database. (might be useful, not sure)

Siteshield - ACL only allowing requests from specific akamai servers (protects against ddos)

ADS - Predictive analytics
Shows the proper ads based on what they are looking at across all sites
Look across 500+ shopping sites, on 160M users
Don't use pixels to allocate ads (slows down the site)

Akamai - Velocitude mobile reformatting on the fly - http://www.akamai.com/html/about/press/releases/2010/press_061010.html
Special tagging system which takes content and displays it for the proper device. Resized images and content done on the fly. Includes all data.

Dnssec
Verisign:
2010 - .NET
2011 - .COM

Akamai implement at end of 2010. Ga early 2011.
signed by Akamai. No need to manage it.
Need to look at godaddy. (they do some of our DNS along with Akamai)
Kpi. You make your own key and keep private key.
Look into internally. Microsoft dns support.
 
Ipv6
Need to start looking into routing ipv6. Check on firewalls (security support for ips and others) lb.
Geolocation for v6?
Look at ipv6 mtu issues
Idea Use Akamai edsgescape for geolocation versus what we do now.
Google support for ga and other tools? We use. Reporting infrastructure.
 
Q4.
Whitepaper
Roadmap
 
Q1 2011
Tech preview

Q1 2012
Limited availability
 
Akamai will nat to v4 for you.

Comments

Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=1171255 (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p