At the Distributed SQL Summit 2020, DaShaun Carter talked about a possible path to cloud native Distributed SQL and Spring at a 101 level. Get the recap. If you are still wondering about it then this article is for you.
_Editor’s note: Below is the final recap from last year’s event. There’s still time to join us live for the upcoming Distributed SQL Summit, Jan 20-22 in India Standard Time. [See the schedule and register._](https://asia.distributedsql.org/schedule)
At the Distributed SQL Summit 2020, DaShaun Carter, formerly a Tanzu Solution Engineer at VMware presented the talk, “Cloud Native Spring for Relational Databases”.
In the talk, DaShaun takes us down about a possible path to Distributed SQL, keeping the discussion at a 101 level.
DaShaun kicks the presentation off by inviting the audience to consider a use case: A Java app, RESTful services, and single node PostgreSQL. For example, an MVP that he wrote 10 years ago, it went to production, and growth happened. DaShaun adds that the app only has value when data is written to the database, like a landing page when collecting a lead, or a sale of something; the write to the database kicks things off. In this use case, you’ve vertically scaled as much as possible, and now you need even more scale. How best to approach this?
SQL stands for Structured Query Language. SQL is a scripting language expected to store, control, and inquiry information put away in social databases. The main manifestation of SQL showed up in 1974, when a gathering in IBM built up the principal model of a social database. The primary business social database was discharged by Relational Software later turning out to be Oracle.
For most of Spring developers, I think you are familiar with the simple auditing features in Spring Data project, but in the past years, it only works with the blocking APIs. The long-awaited Reactive AuditorAware support will be available in the new Spring Data release train.
Distributed SQL Summit Recap: Pinterest's Exploration of Distributed SQL. Learn about the evolution of storage at Pinterest, including HBase, current challenges, & the exploration of Distributed SQL as a viable solution to some of the challenges.
List of Available Database for Current User In SQL Server. Do you know yet? Let's explore it with us now.
The next step in the evolution of database architecture is distributed SQL. Take a look at some of the characteristics here.As organizations transition to the cloud, they eventually find that the legacy relational databases that are behind some of their most critical applications simply do not take advantage of the promise of the cloud and are difficult to scale.