Articles

The Definitive Guide to Building a Data Mesh With Event Streams

,

Data mesh. This oft-talked-about architecture has no shortage of blog posts, conference talks, podcasts, and discussions. One thing that you may have found lacking is a concrete guide on precisely how to get started building your own data mesh implementation. We have you covered. In this blog post, we’ll show you how to build a data mesh using event streams, highlighting our design decisions, and the key benefits and challenges you’ll need to consider along the way. In fact, we’ll go one better: we’ve built a data mesh prototype for you to check out on your own to see what this would look like in action, or fork to bootstrap a data mesh for your own organization. 

Data mesh is technology agnostic so there are a few different ways you can go about building one. The canonical approach is to build the mesh using event streaming technology that provides a secure, governed, real-time mechanism for moving data between different points in the mesh. 

Source de l’article sur DZONE

/par

Agile Integration – What Is It?

,

Have you heard about Agile Architecture practices or about how adaptive methods can help us create solutions iteratively without the Big Up-Front Design? 

Agile Integration arises among these scenarios of constant innovation, where solutions need to be published in ever-smaller development cycles and meet the business needs and the expected time-to-market. We can say that Agile Integration practices are among the main catalysts for accelerating companies’ digital transformation journeys.

Source de l’article sur DZONE

/par

Your job is not to create software, it is to THINK!

,

I’ve got 20+ years of professional experience, and every single place I have worked, I have seen the same anti pattern recurring over and over again. And the « pattern » is as follows; Every single problem has dozens of solutions to choose from. Of course, nobody has the muscles to maintain these solutions, so all solutions ends up becoming sub-optimal, and arguably creates more problems than they fix. It doesn’t matter who you work for, the pattern can be found everywhere; Microsoft, IBM, Google and « John Doe Software Consulting ». This is such a big problem it’s got its own « slogan », which is as follows.

Not invented here syndrom

Source de l’article sur DZONE

/par

Scale Salesforce Apps Using Microservices on Heroku

,

This is the eighth article documenting what I’ve learned from a series of 13 Trailhead Live video sessions on Modern App Development on Salesforce and Heroku. In these articles, we’re focusing on how to combine Salesforce with Heroku to build an “eCars” app—a sales and service application for a fictitious electric car company (“Pulsar”) that allows users to customize and buy cars, service techs to view live diagnostic info from the car, and more. In case you missed my previous article, you can find the link here.

Just as a quick reminder: I’ve been following this Trailhead Live video series to brush up and stay current on the latest app development trends on these platforms that are key for my career and business. I’ll be sharing each step for building the app, what I’ve learned, and my thoughts from each session. These series reviews are both for my own edification as well as for others who might benefit from this content.

Source de l’article sur DZONE

/par

How Scrum Helps Developers Build Technical Skills and Flexible Architecture

,

Developers who tried to build at least one product for an end-user know how many things are essential in a product: thoughtful UX, friendly UI, good performance and stability, security and data consistency, logging and maintenance, etc.
Multiply this to the number of platforms that you have to support. Add marketings and licensing, client support and bug reports, new feature requests, and competitive product pressure.

It’s hard to track everything in one head, and it is even harder to be perfect at every job. That’s why we work in teams. That’s why we use project management processes.

Source de l’article sur DZONE

/par

Creating a Frontend Architecture With Dynamic Plugins

,

The following are some of the most used approaches to handle pluggability on frontend:

  1. The main application works like a layout for all the features it contains, where each feature has switch on/switch off functionality. If a plugin is present, it will be displayed in a certain place. But, if you want to develop a new plugin, you will need to modify the main application, so it will be aware about it.
  2. Load plugins dynamically and add them to the main application as sub-applications in an iframe. That gives certain flexibility, as you can use different versions of the same third-party libraries, but there are also some costs, including:
    • The bundle size blows really fast. All required third-party plugins have to be included inside the plugin again.
    • To reuse already written logic in a core plugin, you either have to copy and paste it or create a shared-module with common functionality and include it in the core and custom plugin. In this latter scenario, when this shared functionality is different from plugin to plugin, it can become a mess really quickly. 
    • It will not allow you to bring smallchanges to an application, like replacing a button with a new one on the fly.

Keeping these limitations in mind, let’s have a look at a new approach. First, I will explain it with a simple example and then on a more advanced level.

Source de l’article sur DZONE

/par

Understanding React Fiber Architecture

,

React 16.0 was released with an update to the React core algorithm. This new core architecture is named “Fiber.” Facebook has completely rewritten the internals of React from the ground-up while keeping the public API essentially unchanged; in simple terms, it means only changing the engine of a running car.

With this release, some new features are also added, like Asynchronous Rendering, Portals, Error Boundaries, Fragments (i.e. return array of elements). Incremental rendering is the headline addition to React, which adds the ability to split rendering work into chunks.

Source de l’article sur DZONE

/par

Speeding Up Development by Splitting the Project Between Teams

,

The case behind this article aimed to complete a large-scale project in a short amount of time. Obviously, you just need to hire a lot of people, and then you have to make sure they don’t hinder each other. The latter is the most complicated; there is no way to make it happen without a good technical approach — and that’s what exactly we are going to talk about.

Our team has been working on a large mobile app for a major telecom company. The app has its "core" functionality (main use cases), and some extensions that offer additional use cases — but, essentially, the app can work without them. Further, we will refer to these extensions as "features."

Source de l’article sur DZONE

/par