Thursday, September 25, 2014

The Cloudcast #162 - Building and Managing Scalable SaaS Services




Topic 1 - Manoj, you and your team came highly recommended to us by the team at Evident.io (Tim Prendergast) and we learned about your service at AWS Summit in NYC. Tell us about your background and how it eventually led you to Loggly.


Topic 2 - You have an excellent talk/presentation on Critical SaaS Mistakes to Avoid. You mention that scalability needs to be priority #1. How much different is building applications/service in the cloud vs. building packaged software?


Topic 3 - We presume that Loggly was built from Day 1 was a web-scale SaaS application. Having built it, what might you do differently or major lessons learned? Realistically, is it possible for someone to SaaS-ify an existing application?


Topic 4 - Let’s talk about Loggly. Every company, every application has logs and they are a cluttered mess of potentially valuable information. People throw them at Loggly. What happens next?


Topic 5 - That has to be a really complex system on the backend to be able to ingest, parse, analyze, tag all the data - keep it isolated by customer - manage historical logs - then visualize it and give recommendations in real-times. Can you give us some sense of what goes on behind the scenes?


Topic 6 - Logging became somewhat more visible at AWS Summit when AWS announced centralized log management. How does your world change when AWS elevates a service that is in your domain?

Topic 7- What are the most common scenarios where companies decide they need help with log management?

2 comments:

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete