SaaSHub helps you find the best software and product alternatives Learn more →
Guides Alternatives
Similar projects and alternatives to guides
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
keda
KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
-
feedback
Discontinued Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! [Moved to: https://github.com/github-community/community]
-
dapr
Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
python-fake-data-producer-for-apache-kafka
The Python fake data producer for Apache Kafka® is a complete demo app allowing you to quickly produce JSON fake streaming datasets and push it to an Apache Kafka topic.
-
azure-dev
A developer CLI that reduces the time it takes for you to get started on Azure. The Azure Developer CLI (azd) provides a set of developer-friendly commands that map to key stages in your workflow - code, build, deploy, monitor, repeat.
-
azfunc-openapi-on-root
This provides sample codes to show Swagger UI on root (/), instead of /api/swagger/ui
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
guides reviews and mentions
- What we talk about when we talk about 'root cause'
- The case for using Rust in MLOps
- Using code as documentation to save time and share context
- Publishing your work increases your luck
-
Pest-Driven Development: Learning, Iterating and Project Planning
Write a more complicated test later. Or refactor the test later. When you're in the moment, you want a test that works. Avoid hard coded values in completed tests, but use them when you're making sure your test doesn't break the very time you write it. A failing test is the starting point of the last decision you made, not the final product. Even if the imaginary people who are going to make fun of your code and call you stupid (ignore this if you're not relating, but if you are read this or watch it) are looking at your public github repo, they're not going to your test suites first. That would be insane. So you can be clunky at first.
- Formatters, linters, and compilers: Oh my
- Two years into this career and already frustrated and burnt out (rant)
- Treat accessibility issues as bugs, not feature requests · GitHub
-
A note from our sponsor - SaaSHub
www.saashub.com | 10 May 2024
Stats
Sponsored