Thank you, Ray.
Thank you all the committee members here.
Thank you.
I'm really glad first of all to be back at Boston for the second time.
Thank you.
And I'm from Chicago, by the way.
And I'm also active community builder.
I run the Chicago Java user's group.
I'm involved now with the VAI, a couple of meetups, too.
So that's me.
And then today I'm going to talk about, actually,
and the reason also is because my company,
it's actually a consulting firm that's based in the US in Ohio.
State of Ohio, although I'm based in Chicago.
So it's about five hours away.
And I recently joined them.
And I'm now called the Director of Emerging Technologies,
doesn't matter.
I'm still doing the same thing, yes.
But essentially, too, I started off as a developer.
So I was developer for over 25 years.
I was able to see Java and then database open source
all these things, and then getting into generative AI
becoming a developer advocate, and now kind of doing this
for consulting firm.
So that's me.
So today, too, I do want to point out this talk
because it's being very short.
Because otherwise, too, I would have some demo to show.
But here, too, I just want to talk a bit high level.
And also kind of making sense, too, for folks in the room.
Maybe not everybody come in here already
have the knowledge in this area.
I'm sure you're all experience in your area.
So I want to make it a bit more friendly, more like,
you know, lowest common denominator thing.
So bear with me if it is too much of an introductory
or too high level.
But yeah, so that's it.
But I want to basically talk a bit more from an architectural
kind of point of view, and also like how, you know,
why is it like we're in cloud native database.
And essentially, too, what it serves, right?
We're building all these fancy things.
We're using all these fancy technology.
But in order to make it useful,
we have to understand what it is good for all these things
and how to do it properly.
So essentially, too, I feel like, you know, cloud native database.
And we're dealing actually with modern data management
these days.
As you know, right?
Like the world is changing.
We're seeing that there are, you know, volumes of data
is increasing everywhere, velocity.
And also there are streaming applications that are data
that's flowing everywhere.
As we all know, data is in many states, too, right?
It can be like data at rest.
That's in the storage, and also like, you know,
in transit during streaming or messaging, and also like,
being processed, right?
As you extract data, you're processing,
it's kind of mid-flight of these things.
So all these, too, we have to take into account
how we manage them properly.
And also, too, as such, right?
Even the world, too, without computer,
it's all these interactions.
So we have to deal with, you know,
the whole user base, like being international,
all distributed, dealing with different languages,
all of these things.
And essentially, too, a lot of these data, too,
it's being like stored in multiple regions as well.
As we can see, we're all like doing in global corporations.
We have data that's being shared across the world.
And they're being shared in different regions.
And we want to make sure we want to reduce latency.
We want to essentially make sure it's resilient.
There's fault tolerance, scalability of these
that modern concerns that we have to work with.
So that's why we're talking in this room.
We're kind of really trying to build the best databases
in the world to handle all these situations.
Okay, so in this modern connected world,
I think I already talked about it most of it,
but just drill down a little bit more, too,
is basically, you know, other than, you know,
real time, we have to deal with that multi-region
dealing with different languages, but also is essentially
to this multiple regions, too, and data as well.
We want to kind of make sure it's comply to
with different like data regulations.
For example, like here in Europe,
there's GDPR and things like that.
So all of the data needs to be really intelligently managed as well.
So we have to worry about high availability
and disaster recovery, all of these things.
And essentially, too, this, actually,
I'm sorry, sorry, but I do have to say,
this is something to our marketing department,
give it to me.
So I have to kind of talk about something.
So we want to make sure, you know, speed and performance
all within acceptable range.
And then make sure, you know, there's data replication,
data access across different regions for high availability
and fault tolerance kind of purposes, too.
And also the work loads itself is massive,
scalability, not just vertical, but also horizontal as well.
And not only that, too, we also have to manage the security aspect
and make sure data is being protected as well.
So, okay, so then like my company, too,
as such, you know, we're consulting and then we're looking
into also helping our clients to develop their applications.
And we're looking to different databases.
So for multi-region support, we have determined that actually
you'll get by databases a very good choice.
First of all, too, it supports low latency.
And essentially, too, it knows how you can enable you to have data
that's store closer to the user, right,
for faster application performance.
So there's a, you have to also remember, too,
if we have multiple regions of data,
you want to make sure whoever is using the data,
you want to have it being available to them closer to them.
So then, you know, the latency won't be as high
of these things.
So you'll get by this as very good, like built-in kind of feature
capability to do that, too.
And also, too, you know, storing data within specific regions.
You also have to make sure, you know, these are sensitive data.
You want to do compliance of these things.
And essentially, business continuity and minimize the downtime
and disruptions.
And then also with automatic failover of these features, too.
And essentially, too, you want to also make sure, you know,
it enables global growth because it can, you know,
help you to kind of expand your database footprint
to without major infrastructure changes, too.
Actually, I'd like to also ask you,
how many of you are kind of more like coming for,
or, I should say, are you mostly developers here
and working with database, or are you maybe like more
from DevOps side, too?
Are they folks also from that side as well?
Yeah, I think both.
But as we find out, too, these days, right,
is essentially, you know, we're developers, too.
We also have to manage the infrastructure side.
So we feel, you'll get by database is really good
discount open source.
It can run it local, or you can also run it on the cloud.
Supports, postgres, consent, and it's all 100% postgres
compliant.
So supports also multiple languages for the client interface, too.
And all of these things listed here are the major languages.
And also, too, essentially, if you kept theorem,
if you're kind of getting into that,
we know that it's actually, it's partition tolerance is high.
Consistency is also high because of the raft,
consensus protocol that Frank already talked about earlier.
And availability, too, is kind of near perfect with this one.
So, but one thing, just really, really,
want to quickly kind of point out for our architectural side of cloud
native distributed database.
We want to make sure resiliency, redundancy,
multi-regional deployment, data reputation,
scalability, as I kind of also mentioned earlier,
and infrastructure automation, all of these are very important, too,
and also the transparency.
So, just be prepared for the future of data.
So, kind of all of these kind of concerns that should be on your list of
kind of importance to do when you're designing and building your data
centric application.
Let's see.
Okay, so these are just some, I know, just such a short time.
So, these are just different links.
You know, they're kind of provided to you.
And these, the sides will be available on the site.
So, you can look at it, and I want to, particularly, point out,
if you want to kind of get your hands into the occupied,
I find this really helpful, this tutorial, too.
Actually, the thing is, I was going to do that,
but it's essentially on the occupied website.
So, you can follow that, too, is kind of getting to your distribution
and the outages tolerance as well.
So, that's that.
And also, I have my own stream that actually,
I do more hands on, if you want to follow me,
that's on Twitch, and also on YouTube, too.
And then, this one, I don't want to talk about, but if you want any
consulting work, you can come talk with me, too.
And this is how you can see in touch with me.
So, thank you very much.
I know it's kind of a whirlwind, but, yeah,
but just so you know, I'm here, I can, I'm happy to help, too.
So, thank you very much.
Yeah.
Thank you.