You can save time by going DB first and then replace the generated API step by step with a custom one once you've got more resources.Īs you can see, you're able to move at an extremely fast pace without depending on a specific vendor. Or, start with one approach and then slowly move towards the other. You can build your backend using NestJS or just plug in your PostgreSQL DB and use it right away. Bring your own APIs and databases, and put your own user interface on top, but everything in the middle, you shouldn't worry about. Think of WunderGraph like a full stack framework that does all the heavy lifting of security, authentication, authorization, caching, etc., while leaving the "head" and the "tail" completely up to you. In the future, we'd like to support Kafka and many others, but it's really up to you what you'd like to plug into WG. These could be GraphQL or REST APIs, or even Databases. You will be able to generate a Java client, Svelte, Vue, iOS Swift or anything else in the future.įinally, what do we mean by backend agnostic? WunderGraph generates an API from all the DataSources you define. So, by "Headless" we mean, WunderGraph doesn't force you into a specific API consumer / frontend stack. We will extend support for other languages and frameworks soon. Currently, we're supporting TypeScript, React and NextJS. Additionally, you should be able to connect DataSources of any kind, making your whole stack portable to different environments.Īs you might know, WunderGraph generated clients if you want. Vendor independent means, you should be able to use WunderGraph anywhere you want, on your laptop, on any public or private cloud. WunderGraph has the vision to become a vendor independent, headless, backend agnostic API Integration framework. WunderGraph - headless FullStack while being backend agnostic If you'd like to get informed once we're releasing it, sign up using the following form. One part of our strategy is to open source our framework using a MIT license. Do you really want to build on top of a proprietary layer of software? Nobody can easily copy their Workers implementation. It's counter-intuitive but Cloudflares moat is also their weakness. It's not easy what they do, but the "integration layer", in this case the docker container, is open and not proprietary. If they go broke or change their business model, I can run my container on one of their competitors. Fly "simply" hosts a docker container for you on the edge. I personally would much rather prefer a service like fly.io over Cloudflare Workers. Services like Cloudflare Workers for example offer an amazing functionality, but you have to rely on a single provider, you cannot easily eject their service or run it on your own. We don't just want to create a great DX for working with APIs, we also want to build a tool that prevents vendor lock-in automatically. Avoiding vendor lock-in by using open standardsīuilding on top of RDBMS like PostgreSQL, MySQL, SQLServer and SQLite means that you can choose from different providers, you're not locking yourself into a specific vendor, which leads us to our secondary goal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |