dapr
nextjs-tailwind-ionic-capacitor-starter
Our great sponsors
dapr | nextjs-tailwind-ionic-capacitor-starter | |
---|---|---|
77 | 9 | |
23,218 | 1,546 | |
1.0% | - | |
9.7 | 5.6 | |
6 days ago | about 1 month ago | |
Go | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dapr
-
Interesting projects using WebAssembly
The following two examples are open-source projects maintained by Fermyon with contributions from companies like Microsoft and SUSE. The first is Spin, which allows us to use WebAssembly to create Serverless applications. The second, SpinKube, combines some of the topics I'm most excited about these days: WebAssembly and Kubernetes Operators :) The official website says, "By running applications in the Wasm abstraction layer, SpinKube offers developers a more powerful, efficient, and scalable way to optimize application delivery on Kubernetes." By the way, this post shows how to integrate SpinKube with Dapr, another technology I'm very interested in, and I should write some posts soon.
-
Comparing Azure Functions vs Dapr on Azure Container Apps
Azure Container Apps hosting of Azure Functions is a way to host Azure Functions directly in Container Apps - additionally to App Service with and without containers. This offering also adds some Container Apps built-in capabilities like the Dapr microservices framework which would allow for mixing microservices workloads on the same environment with Functions.
-
Episode 150: myNewsWrap – SAP and Microsoft
Having containers is nice but everything (well ... nearly everything 😉) gets better with Dapr as an outstanding tool for app development in the container-based area. Here we go what might be worth a look:
-
Ensuring Seamless Operations: Troubleshooting and Resolving Dapr Certificate Expiry
A CNCF project, the Distributed Application Runtime (Dapr) provides APIs that simplify microservice connectivity. Whether your communication pattern is service to service invocation or pub/sub messaging, Dapr helps you write resilient and secured microservices. Essentially, it provides a new way to build microservices by using the reusable blocks implemented as sidecars.
I had no overview of the Dapr system which caused me a lot of time in trying to get to the root cause. So first thing I did was to create a nice dashboard where we can have an overview of our Dapr services and their certificates. I started from the official one from Grafana for this. But the dashboard is a bit outdated so I had some issues with the queries, so I did some changes and you can find the JSON of the dashboard below if it helps anyone.
-
Modular Architecture Design question | Re-using modules in multiple applications
I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.
-
Ask HN: Modern Node.js Request Fault Tolerance Library?
Just heard about Dapr last week. Might be more than what you are asking, though but it’s probably worth a look.
-
Creating a Dapr pluggable component for Supabase
From my perspective, I’d like to explore further how Dapr can integrate with other Supabase features. It would also be great to see a Supabase state store as a built-in component that’s available in the Dapr runtime without the need of running the pluggable component separately. I also hope the proposed DocumentStore building block will get some traction this year, since this will pair up very nicely with Supabase and other PostgreSQL stores.
-
Kv.js
Could you use Kubernetes to solve this? Have a single pod running the Redis instance and then multiple running Node.js talking to the Redis instance via something like DAPR (https://dapr.io/)
-
Anything close beam/otp for other languages?
Dapr is also building a workflow orchestrator into their microservice system. It's almost in Beta, and when you combine it with Dapr's Virtual Actors, it looks powerful. It will also let you integrate a workflow engine like Temporal, too. https://dapr.io/
nextjs-tailwind-ionic-capacitor-starter
-
Solito – React Native and Next.js, Unified
This looks cool! If you’d like to have a single web-based codebase for iOS/android/pwa/etc using Next.js then you might like this approach using Capacitor: https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st...
The benefit over using RN for this is being able to use libraries like Tailwind on all platforms, etc
wow, that's a weird limitation.
The README says: "SSR is currently disabled for the Next.js app as the app will be fully client-side rendered for iOS and Android. This is a limitation we are working to address in a future update."
I guess it's because CapacitorJS pre-bundles the entire PWA for the App Stores:
"Of course, you also could load the app completely remotely by changing the server.url configuration for Capacitor to point to your SSR'ed Next.js app, but that has other challenges such as App Store approval if the app doesn't check the boxes for Apple to qualify it as an app that has enough native integration (at that point this is on you, not Capacitor)"
https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st...
But I don't understand why SSR would be disabled for the NextJS PWA on the web?
Maybe Max Lynch aka. @mlynch aka. @yesimahuman could provide some insight here.
-
Any recommendation to port a production SPA to Nextjs?
Max Lynch from Ionic has a great repo demonstrating this. He uses it to get Next to work with Ionic and Capacitor but the idea is essentially the same.
-
Next.js 12
Agreed! Next.js works great with this model! I’d recommend Capacitor over Cordova (similar but more modern). Here’s an example: https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st...
-
Build Mobile Apps with Tailwind CSS, Next.js, Ionic Framework, and Capacitor
If you're confused by all the project names and how they work together, don't worry, I'll break down each part of the stack each project is concerned with, along with some visuals and code samples demonstrating how all the projects work together. At the end I'll share a starter project with these technologies installed and working together that can form the foundation of your next app.
What are some alternatives?
MassTransit - Distributed Application Framework for .NET
camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers
tye - Tye is a tool that makes developing, testing, and deploying microservices and distributed applications easier. Project Tye includes a local orchestrator to make developing microservices easier and the ability to deploy microservices to Kubernetes with minimal configuration.
Next.js - The React Framework
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
Nomad - Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
go-micro - A Go microservices framework
go-kit - A standard library for microservices.
vike - 🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
supabase - The open source Firebase alternative.
kubernetes - Production-Grade Container Scheduling and Management