(bouncy music)
>> Welcome to this Cube Conversation, I'm Lisa Martin.
I'm joined by Erez Berkner,
the CEO and co-founder of lumigo.
Erez, welcome to the program.
>> Hey Lisa, thank you for having me.
Glad to be here.
>> Excellent, we're going to have a great conversation.
We're going to be talking about the growing trend
of using cloud native and serverless.
But before we do, Erez,
give our audience an overview of lumigo.
>> Excellent, so lumigo is an observability platform.
Basically allowing developer, architects,
the technology person in the organization
to understand what's going on with his modern cloud,
with his serverless, with his cloud native application.
So at the end of the day, lumigo as assess platform,
allow you to know what's happening, get visibility,
and be able to get to the root cause of issues,
many times before they actually hit your production.
>> I saw on your website, in terms of speed,
getting up and running quickly,
in four minutes with four clicks.
Tell me how developers do this that quickly.
>> Yeah, that's actually great point.
Because in general, when we talk about the modern cloud,
people are really fed up with deploying agents,
long processes of servers,
and more and more we see the trend towards APIs,
toward code libraries.
At the end of the day, at the heart of lumigo,
we built a very strong automation engine
based on APIs, based on lomdalier integration.
And this allows a developer to basically connect lumigo
via the APIs in couple of clicks.
Doesn't require code changes, deployment of agents,
deployment of services.
And this is why it's so fast, because it's lightweight.
And that's a trend of managed services, of serverless,
and lumigo is another stone in that wall.
>> Excellent, lightweight, key there.
Define serverless, what is considered serverless?
>> Mmm, ooh, don't get me involved
in dispute of those definitions.
But I can share my view, but this is a..
Anyone, I would say, have his own definition.
But the main concept with iC serverless
is at the end of the day,
really, like it says, serverless.
You don't deploy a server.
You don't rent a server, you don't manage a server,
you don't deploy an operating system,
you don't patch a server.
You don't take care of scalability, of high visibility.
Basically, all the chores of managing,
of maintaining a server, basically go away.
Now, they don't really go away.
Somebody else is dealing with them.
So there is a server, but it's not your server to manage.
And that someone is a cloud provider,
is Amazon, is Microsoft, is Google, it's IBM.
And this is how I view serverless.
Basically, a managed service that doesn't require
to deploy or manage a server,
and you use it via APIs.
And if you think about that,
in the past when serverless started, 2015,
serverless was function of the service,
Lambda, AWS started that.
But today, in 2021, serverless,
yeah, it's functional service, it's Lambda,
but it's also storage of the service, like F3,
and data to service, like Snowflake, like DynamoDB.
And queue service like SNS, like EventBridge, like Kenesis.
And even Stripe, payment of the service,
and Twilio, and SendGrid.
So all these API based services, that you just consume,
and they're like Lego pieces that you connect together
and you just connect and you go,
and you start working and they up and running,
this is how I define serverless today.
And that's basically allowing you to run
any application today with zero servers.
>> That's a great definition, that nice and clean,
and I think the Lego bricks
really kind of clicked in my mind when you talked about that.
Let's talk now about
for business critical production applications,
what are you seeing in terms of
adoption of serverless for those cases?
>> That's a great question,
because I think that we are in a critical point of time,
in cloud native, in modern cloud, in serverless market.
And I think it's an evolution.
You know, when we started, again, back in 2015,
serverless with just one or two services.
But we got to a critical mass of services,
including DynamoDB and ESRI and Lambda and EventBridge
and all the other services, that's their function,
that basically allow you to build your application
based on serverless.
And this critical point of the architecture of service
being mature enough, being wide enough,
to allow you to do what you want,
to have the confidence running serverless in production,
to know that you have the tooling
that you used to have in the past
to monitor, to debug, to secure, to understand cost,
all of this are really coming together this year.
We actually see this year, and a bit of end of last year,
but this is what's driving a trend in the industry.
I think it's still not known enough
to many of the organizations,
or not wide enough, or not public enough.
But our customers are focused
on cloud native and serverless.
And we've seen a dramatic change in the last six months.
And the main change is
organizations that used to play around with serverless,
that used to do non-business critical usage of serverless,
because it's easy, because it makes sense,
because it's fast,
all of a sudden they got the confidence
to do that with their business critical application
in production.
And this is a shift that we're seeing.
And that goes many times with the technology maturity.
You start, you play around with something, it makes sense,
it makes sense, you get confidence, and boom!
This become more and more mainstream technology.
And we're at the verge of that.
>> In terms of a catalyst for that confidence,
do you think that the events,
the world events of the last 12 months
and this acceleration of digital transformation,
has that played any part
in the maturation of the technology
that's giving customers the confidence to adopt serverless?
>> Yeah, I think it's fascinating, what we're seeing.
Because I think the last event
really push a organization to innovate.
Because of different reason,
because they don't have the head count,
so they need to reduce the maintenance that they do,
they need to reduce the developer head count,
the DevOps head count, they need to reduce costs.
Serverless is running only when it need to run,
so you pay only for what you use.
So this is another method that our customer,
for example, reduce their cost.
So I think beyond the maturity of the architecture,
the push forward for optimization,
for lower usage or lower usage of engineering force,
really pushed serverless forward.
And this paradigm, once it worked for one team, it's viral.
It's viral with in organization and the cross-organization.
So this team managed to reduce 50% of the cost,
and 70% of the developers
that need to maintain the production.
Let's duplicate that.
And let's do that four times, and five times, and 10 times.
And this is the point in time that we are.
So that's a trend and I think it's very much impacted
by the world economics.
>> Interesting, that trend of virality.
Let's dig into, you mentioned a couple of benefits.
I heard reduction in total cost of ownership, or costs.
Talk to me about the lumigo solution, the technology,
and what some of those key benefits are
that it is consistently delivering to your customers.
>> So I think the basic is that serverless
makes a lot of sense, economical, maintenance.
That's why the cloud providers
are putting so much effort and power
in delivering more and more serverless maturity.
One of the challenges that we see
for almost any organization adopting the new technology,
it goes back to we understand the values,
but at the end of the day I need to make sure
that if something goes wrong in production,
I will know about it and I will know how to react
and fix it in a matter of minutes.
'Cause that's my service, that's my business.
And I know how to do it in a server world,
where there's one server or three servers,
and everything running in the same server.
I have the tools for that.
And I want to go serverless, I want to go cloud native,
but all of a sudden there are dozens of services
that I consume via APIs
and they're a part of a bigger picture of my application.
So I'm lacking many times the confidence,
the tools, the awareness of,
something goes wrong, I'll know about it,
and I'll be able to fix it.
And this is where lumigo comes in.
So we built lumigo from the ground up
to be very much focused on the modern cloud, on serverless.
And that means two main things that we provide
for our customers.
One is, I would say one thing.
We provide confidence.
You can use serverless in production,
and you can rest assured that if something goes wrong,
you will be the one alerting
and we'll give you all the information to debug it.
And we do it by two main things.
One is the visibility that we create.
Because we're connected to the environment,
we alert on things that are relevant to serverless.
It's not about CPU, it's not about a iO.
It's about concurrency limits, it's about cold start,
it's about time outs, it's about reaching duration limits.
These are the things that we know to alert you about.
It's very specific to the serverless services.
And it's not a generic metric, it's serverless metric.
So that's number one, visibility,
getting alert whenever something is about to go wrong.
But what do you do then?
Let's say I have one million invocations a day,
and one of them is actually, I have a trigger,
something went wrong.
And this is where lumigo allow the developers to debug.
Basically, you click on a specific issue,
and lumigo tell you the entire story of what happened,
from the very beginning, an API gateway triggering a Lambda,
right into DynamoDB, triggering an Lambda,
it tell you the entire story end to end
of what happened with that specific request,
with inputs, with outputs, with environment variables.
All the things the developer need in order to debug,
to find the root cause,
and then fix it in matter of minutes.
And that's the game-changer that allow those organizations
to run serverless with confidence.
>> You talk about confidence,
it's a word that I hear often
when I'm talking with customers of vendors.
It's not something to be underestimated.
It's incredibly important that technology
provide that confidence,
especially given the events
of the last year and a half that we've seen
where suddenly folks couldn't get into data centers,
for example.
Talk to me a little bit about some of the customers.
I saw from your website some great brand names,
but talk to me about a customer
that you think really not only has that confidence
that lumigo is delivering,
but is really changing their business
and their approach to modern monitoring with lumigo.
>> Yeah, so there are several interesting.
I'll choose maybe one of the more interesting cases,
a company called Medtronic.
It's one of the largest medical device companies in the U.S.
And it's very interesting because they have an IoT backend.
Basically they have medical devices around the world
that send IoT information back to their cloud.
And they get metrics, they run machine learning on that.
And they took a strategic decision
to run the system with serverless.
Because it can scale automatically,
because it can deploy one more million devices
and they don't need to change anything,
and many, many other benefits of serverless.
And we met them back in 20, end of 2019.
They were looking for exactly a solution
that allows them to get issues
and drill down to analyze those issues.
And they were just in the beginning.
The early days they had 20 million invocations,
requests per month.
They knew they were going to scale,
they knew that when they scale,
they cannot correlate logs,
and try to understand what happened manually.
They need a professional tool.
And this is where they started using lumigo.
And today, a year and a half after,
they reached one billion invocations a month.
Again, the same concept, IoT devices, medical devices,
sending metrics and information
for the backend for processing.
And today,
lumigo is monitoring everything in that environment.
And alert them from, you're about to have a problem,
or you have an application error,
or you have high latency, you have spike of cost,
all of that are covered by lumigo.
And the developers, once they get this to slot,
to play the duty, you're just able to click on it,
and drill down and see, one by one,
requests that created the trigger that alert.
And they can understand, again, the inputs, the output,
the logs, the return values, everything.
I call it debugging heaven.
Because it's always there, it's always post-mortem,
you don't need to do anything.
At the same time you get the visibility and you can fix it,
because this is their production,
this is their business critical application.
>> Debugging heaven, I love that.
That's for developers, that is probably a Nirvana state.
I want to wrap up Erez,
just giving our folks in the audience an overview
of the relationship that lumigo has with AWS.
>> AWS is one of our strongest partner.
I think there's a great synergy working with AWS.
We've been partners for the last three years.
And I think the reason for the...
You know, we're still...
AWS has thousands, tens of thousands of partners.
I think that this partnership is specifically strong
because there is a win-win relationship over here.
On the one hand side lumigo is very much invested on Amazon.
Our customers are mostly Amazon customers,
and we are solving, providing confidence for those customers
to run serverless in production,
and answering a need of a customer.
And this is also the win for Amazon.
Amazon is basically have
a great, great technology of serverless.
But the lack of visibility, the lack of confidence,
is hindering the adoption.
And Amazon decided to work with lumigo,
saying, we'll develop the core, we'll develop the services,
we'll develop the serverless architecture,
and you can use lumigo for monitoring, for debugging,
for everything that you need
in order to run that in production.
And that's been very, very strong relationship
that just grows as we develop together.
And it's been on working together with customers,
introducing customers,
but also on the technology level.
For the audience who sees Amazon announcement on serverless,
many times lumigo is a design partner.
It's part of the announcement,
of lumigo was a design partner and the launch partner,
and support the new feature out of the box.
This is because we want to get the support
as soon as possible,
as soon as new features are released.
So that's where we are today.
>> Sounds like a very collaborative
and symbiotic relationship.
Erez, thank you for joining me on the program today,
talking to us about some of the trends in serverless,
some of the things that are catalyzing adoption,
that visibility, that confidence,
that lumigo delivers to its customers.
We thank you for your time.
>> Excellent, thank you very much Lisa.
Have a good day.
>> You too!
For Erez Berkner, I'm Lisa Martin.
Thanks for watching this Cube Conversation.
(bouncy music)