The Data Mesh - should you adapt?

In actuality, not every firm may be a good fit for the implementation of a Data Mesh.  Larger enterprises that experience uncertainty and change in their operations and environment are the primary target audience for Data Mesh.  A Data Mesh is definitely an unnecessary expense if your organization's data requirements are modest and remain constant over time. What is a "Data Mesh"? As it focuses on delivering useful and safe data products, Data Mesh is a strategic approach to modern data management and a strategy to support an organization's journey toward digital transformation. Data Mesh's major goal is to advance beyond the established centralized data management techniques of using data warehouses and data lakes. By giving data producers and data consumers the ability to access and handle data without having to go through the hassle of involving the data lake or data warehouse team, Data Mesh highlights the concept of organizational agility. Data Mesh's dec

Thinking to Switch to Vue? A Ligthweight but Powerful Framework

Since I started working developing user interfaces with GWT, several years have passed and I have gone through different technologies, such as Angular V1.x and V2.x. Now arriving with Databloom, I met Vue (v3.x). I have been lucky to see how browsers have grown to become capable of not only displaying informative content but also of becoming a multipurpose box, capable of offering functionality of all kinds, which was previously only available in specialised standalone applications developed in Java, or C , VB, etc.
Each of these and other technologies that have passed allowed us (developers) to shape various functionalities to the content displayed in the browser, limited only by the imagination and needs of the requirements. However, unlike years ago, we now find ourselves with powerful front-end tools and frameworks, which not only allow us to build web applications, but also give us the job (and the alternative) of knowing which one to choose according to our needs. In this decision a series of factors are combined that can help us to appropriately choose the frontend technology that best suits our needs and that allows us to develop our applications making the most effective and efficient use of the resources of our organisation: previous experience of the development team, age of the team, deadlines for our commitments, fashions, among which I have found myself in the different companies in which I have worked.

Databloom has opted for a decision based on the relationship between the speed of adaptation of the technology vs. the cost of learning. 
Considering the richness that the framework offers according to our needs, we decided to adopt Vue 3 to build our frontend.
We have been working with this "new" framework for several months now and we have found only pleasant surprises in the process of building our application: a lightweight framework, with all the power of the "biggest" framework. Furthermore,

Vue is powered by many plugins that they complement the gaps that it has, but with the advantage of offering a much smoother learning curve.

Today, even novice team members, with no previous experience in front-end development, have a much friendlier experience, allowing them to add value to their product in a much shorter time. In addition, if you come from Angular 2x for example, the learning and adaptation will be even more natural and you will be able to take advantage of everything that concerns Typescript in the construction of your components.
I must say that not everything is perfect. There are things to keep in mind about Vue 3 vs other more structured frameworks that I did not like so much. For instance, saying that when working with the "Composition API" mode, there are variants of it that make the creation of the component (tag <script>) not as transparent as one would like. Yet, they offer one or another advantage vs the cleaner option (<script setup lang=”ts”>) that is more similar to how the controller layer is built a view in Angular 2x for example. Same with the view-model hooking process which forces you to wrap your property in an object (ref, reactive, swallowref, etc) and at first glance it's not as intuitive as just defining a property in the controller and binding it in sight. Nevertheless, once you get used to these details, you can use them to your advantage and you will have different options to handle the various scenarios that can arise in the process of building your application.

We have found a powerful ally in Vue when building the face of our system Blossom (The Blossom Studio) 

Using Vue, we hope to develop and offer a robust product that is useful and effective tool for optimization activities in processing. of “Big Data”.

Popular posts from this blog

Towards a Learning-based Query Optimizer

The Missing Piece in Learning-based Query Optimization

Federated Learning (Part II): The Blossom Framework