Systems | Development | Analytics | API | Testing

What is data fabric architecture? The case for data fabric 4 key facts about data fabric architecture Data fabric architecture can modernize and future-proof your data approach Data fabric architecture is a virtual data layer that connects any number of external systems together to provide unified access and a complete, 360-degree view of an organization’s data. Whether your data lives in legacy systems or multi-cloud environments, a data fabric can connect these systems together for a unified view.

Today’s fans are global - often based across the world from their favorite team, sports star, or artist; and they are also virtual - for example, 99% of NBA fans across the world will probably never set foot in an arena. These trends are driving a shift in not only fan behaviors, but also expectations. Fans engaging in live events virtually rely on applications to deliver rich realtime experiences with such low latency and reliability that it can almost replace the in-person experience.

Web applications have become the backbone of businesses—from eCommerce platforms like Amazon to social networks like Facebook. Unlike traditional websites that simply present information, web apps let users interact, make transactions, or even collaborate in real-time. Whether you're a small startup looking to streamline operations or a large enterprise needing scalable solutions, web apps make it all happen. But how do you go from idea to execution?

A development environment is a crucial setup of tools, configurations, and processes that developers use to build, test, and deploy software. Whether it’s a local setup on a developer’s local machine or a remote cloud-based solution, a development environment’s primary goal is to provide a seamless space where code can be written, tested, and executed efficiently. It’s never been more important to have a streamlined setup of cloud and development environments.

In the first part of this series, we created a Django online shop with htmx. In this second part, we'll handle orders using Stripe.

Picture this: a customer reaches out with a seemingly simple request—convert a date field to a different format in their API responses. The catch? They only have read-only access to their database, which means no schema updates, no new columns, just pure data transformation. This intriguing challenge led us down the rabbit hole to rediscover one of DreamFactory's most powerful yet underutilized features: enhancing API calls with SQL functions.

System administrators, DBAs, and application developers all know about the need for data integration. That’s when you have to pull data from one database, application, or web service to another. Fortunately, this task is a lot less challenging than it used to be because APIs (application programming interfaces) are so popular today. APIs provide a standard way to share the data and services of one system with another, even if the two systems are otherwise incompatible.

When you build an app, you'll often find that certain tasks do not require user interaction and are better performed in the background. Elixir provides excellent primitives, such as Task.async, to offload these tasks from the main user pipeline. Additionally, libraries like Oban offer more control over background tasks when needed. There's also FLAME, which the core Phoenix team is developing to offer a scalable solution for offloading intensive tasks to remote machines.