Why don't you create your next application without a database? by Rudy De Busscher

Подписаться 158 тыс.

Просмотров 4,4 тыс.

50% 1

Within every application, data plays a very important role. Currently, we always use a database or a No-SQL solution to store our data externally to the Java process. But this comes with a cost, the impedance mismatch between the object-oriented world of Java and the external data storage. And developers spend a lot of time creating the mapping, writing queries, and optimizing the retrieval from the external system.
With MicroStream the data instances within the JVM memory ARE your database. You can query them using the getter methods and the Stream API with extremely high performance and low latency as no mapping or external retrieval is needed. Your Java objects survive the JVM restart because they are serialized to disk for example with a new, from the ground built up very secure serialization solution.
In this session, you will learn about the revolutionizing way of data storage with MicroStream. The basic principles, how it works, and demos are part of the agenda of this session.
Rudy De Busscher
Rudy loves to create (web) applications with the Jakarta EE platform and MicroProfile implementations. Currently, he is a Developer Advocate for MicroStream. He has implemented various projects in a team for customers, helped various Open Source projects (Apache Myfaces, PrimeFaces, DeltaSpike, MicroProfile, ...), and supported Developers and teams. He is also working around Web Application Security using OAuth2, OpenId Connect, and JWT.
------------------------------------------------------------
INTRO
* visuals & editing by @Mercator
* music : Avocado by Ephixa

Опубликовано:

30 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@timmelis4872 Месяц назад

Another awesome and inspirational talk from Rudy ...

@georgeFulgeanu Год назад

I feel like it's an awful idea for the next reasons: 1. You completely kill any chance of data analytics based on db queries - you have to move all the data you need to the logs 2. In a containerized world, the footprint needs to be small, the in memory model couldn't keep years of data in memory without a big overhead. 3. A database can handle multiple connections, our containers that load up in memory would be isolated, if they're not isolated and it's a common persistence layer, how will it handle reads and writes? What about ACID principles that you learn in faculty? Are there any people that use these and we can get some data, case study, FAQ?

@TNothingFree Год назад

1. It doesn't kill data analytics, he mentioned it can be combined with common practices. 2. Solutions is either to archive it or use a long-term storage, both can be applied without the installation of a Database. (Disk management). You are right it might be a problem to some applications. 3. Shared memory synchronization or locking of some data, what he talks about is more the serialization part - the ability to store objects. In either way there are good solutions for that. We use this kind of in-memory solutions mainly for caching or keeping up local copies. "Multiple connections" are a problem to DBs as well, we had ton of issues because of multiple connections. Nothing is a silver bullet, sometimes the cost of a DB exceeds the need of a real DB. 1 TB harddrives aren't expensive, and you can keep in memory + Paged + Synced files for you applications as long as they are small. Conventionally - scaling it is much harder and better solutions exist for scale. Another term to think about is the design process - Too many products are designing around a DB instead of focus on business solution - leaving SQL everywhere and data classes which match the DB architecture. Ultimately coupling itself into the DB. Your App is not your DB.

@suikast420 Год назад

@@TNothingFree I think you complete missunderstood the goal of a sql or nosql database. There is lot of stuff there. Multi tendandcy User and userright management ACID Multi data regions Data history tracking Data indexining The goal of an approach like microstream does can be well fit for comuptation models or level2 caching for example. But it wil be never ever replace a database. Until you make all your apis serialisable 😀