Find out how to get the same DX wins of Vercel Storage by using its Postgres, Redis, and Blob providers with WunderGraph — a free and open-source technology without the Vercel markup, and without vendor lock-in to boot. — Vercel’s making quite the push for serverless, lately. It announced a whole fleet of services at its Vercel Ship virtual event, with the biggest bombshell being storage — Postgres, KV, and Blob — all “re-imagined from the perspective of a frontend developer,” and critically, all serverless.

Apollo Router’s Elastic license preventing adoption? Want to go even faster? This open-source Federation gateway has got you covered. — Enterprises have diverse data dependencies — internal microservices with specialized data domains, legacy systems with proprietary data formats, and third-party APIs and SaaS applications with their unique data models and endpoints. TL;DR: different (and often legacy) technologies that need to be brought together, somehow.

Federated GraphQL architectures are the way forward for modular microservices-based development. But what happens when you need more than just your standard, garden variety unified GraphQL schema? — What does GraphQL look like in a world that is transitioning from monolithic architectures to microservices? In an ideal version of this world, your monolithic backend would be modularized and factored into discrete services with well-defined boundaries. You’d have a GraphQL server (graphql-js, Apollo Server, graphql-yoga, etc.) for each backend…

Because a thriving GraphQL ecosystem cannot be built upon closed, proprietary solutions from a single vendor. — GraphQL is great in that it truly decouples the frontend from the backend, allowing developers to focus on data needs without being tied down by the specifics of the underlying APIs…or needing to be omniscient about which microservice needs to be hit up for which part of data. This whole…

How do you effectively migrate away from monoliths without getting stuck in Adapter Hell? Let’s talk about the synergy between BFFs and the Strangler pattern, featuring WunderGraph. — The idea of having loosely-coupled services as the primitive building blocks of a system — as opposed to monolithic development — isn’t exactly a hot take. Microservices offer modularity, independent scalability, and the ability to change, fix, and adopt new things as and when needed.

Crucial takeaways from building production-ready BFFs that every developer should know. — A Backend-for-Frontend (BFF) is a specialized server-side API that serves as an intermediary between the frontend (client-side) applications and various downstream APIs, aggregating and transforming data as needed before delivering it to the frontend. Why build BFFs? They’re a façade — shielding your frontend from the complexities of dealing directly…

Integration, Unit, and E2E testing aren’t mutually exclusive, but they sure are a pain to implement in a BFF system. Could WunderGraph’s type-safe testing and mocking library make this easier? — With the Backends-for-frontends (BFF) pattern, you build servers that are an intermediary aggregation layer, orchestrating multiple API calls to provide one specific API, tailored to the needs of a specific client.

The BFF pattern optimizes backends for specific client interfaces. Using GraphQL for it fixes some of its drawbacks, but can we do better? Let’s find out with WunderGraph. — The Backends-for-frontends (BFF) pattern, first described by Sam Newman, and first used at SoundCloud, is an effective solution when you have multiple client platforms — web browsers, mobile apps, gaming consoles, IoT devices — each with unique requirements for data, caching, auth, and more.

Silos slow down your entire organization, and degrade your Bus Factor to dangerously low numbers. Find out how to build a culture of knowledge sharing to avoid that — making sure critical expertise is transferred, not hoarded. — Knowledge is power. Organizations that institutionalize and share knowledge (thus creating processes that can be explained clearly and reliably to their employees) generate value, consistently.