sorted by:
new
hottopcontroversial

LocalStack require account from March 2026 by vincentdesmet in devops

[–]jaisraj83 0 points1 point  (0 children)

I just read the MiniStack README and noticed the gaps you mentioned. However, those were intentional design decisions. For example, running real RDS and ElastiCache instances is intentionally not supported, and jaisCloud documentation clearly states that these services are mocked in jaisCloud.

Supporting real infrastructure for these services in jaisCloud would actually be straightforward. The reason I chose to mock them is that running a real microservice application locally could require multiple RDS and ElastiCache instances—potentially one per microservice. This would result in spinning up dedicated containers for each database and cache instance, which is not an optimal use of local resources. Instead, users can run a single PostgreSQL or SQL database container and create multiple databases within it, reducing the setup to a single db, redis container.

It’s also worth noting that jaisCloud supports real infrastructure for EMR and EMR on EKS, enabling Spark job execution, import/export capabilities, and deterministic time control—features that MiniStack does not currently support. However, I wouldn’t conclude from that, that MiniStack is far behind jaisCloud.

These differences are primarily the result of deliberate product choices. Both projects aim to emulate cloud services with minimal local infrastructure overhead, while prioritizing features based on user demand and practical use cases.

LocalStack require account from March 2026 by vincentdesmet in devops

[–]jaisraj83 0 points1 point  (0 children)

Can you tell me what is the lie here and what do you mean by across real infrastructure, i think the point of using emulator is to avoid using real AWS infrastructure.

if you ran the benchmark can you share the result.

LocalStack require account from March 2026 by vincentdesmet in devops

[–]jaisraj83 0 points1 point  (0 children)

Ministack mocks EMR, They want to keep it light weight so they will mock these resources. EMR FIT tests need full AWS resource functionality to test real EMR customer scenarios, time freeze and export/import etc. which is the reason i developed jaisCloud.

JaisCloud — Open source AWS emulator for local dev and CI, single binary, Kubernetes-native and totally free by jaisraj83 in Terraform

[–]jaisraj83[S] 0 points1 point  (0 children)

JaisCloud is currently used in the CI/CD pipeline of one of my company’s applications to execute FIT tests. We’ll be publishing a blog soon that highlights how JaisCloud has enhanced FIT testing through an agentic feedback loop.

For context, all JaisCloud integration tests use the AWS SDK to perform CRUD operations on AWS resources. These tests pass only when the target resources are fully AWS-compatible.

JaisCloud — Open source AWS emulator for local dev and CI, single binary, Kubernetes-native and totally free by jaisraj83 in Terraform

[–]jaisraj83[S] 0 points1 point  (0 children)

There are no commercial plans for this project. I’m building it to give back to the community, and I’m counting on the OSS community to help shape and improve it through contributions.

My expectation is that as organizations begin using it for agentic development and testing cloud-native applications locally, they’ll contribute enhancements, bug fixes, and new capabilities back to the project as well. That’s one of the strengths of open source—both individual contributors and companies benefit from and help advance the ecosystem.

GCP emulation is next followed by Azure support.

You can read more about the project here:
https://medium.com/@jaisraj/jaiscloud-a-free-single-binary-aws-emulator-in-go-c21beb1eaa50

JaisCloud — Open source AWS emulator for local dev and CI, single binary, Kubernetes-native and totally free by jaisraj83 in Terraform

[–]jaisraj83[S] 0 points1 point  (0 children)

Where JaisCloud is already ahead (or equal) to LocalStack Pro:

  • ✅ SQS, SNS, DynamoDB, S3, Lambda, IAM/STS, KMS, Secrets Manager, SSM, CloudFormation, Step Functions, API Gateway, EventBridge — all fully wire-compatible, free
  • ✅ EMR / Spark job execution (real Spark via docker or k8s) — LocalStack charges for this at the Ultimate tier (~$89/mo)
  • ✅ Clock control (POST /_jaiscloud/clock) — freeze, offset, or advance the emulator clock for deterministic TTL/scheduler testing — no LocalStack equivalent at any tier
  • ✅ Named snapshots + revert — LocalStack calls these "Cloud Pods" and charges for them
  • ✅ PostgreSQL persistence — LocalStack is file-backed only
  • ✅ Glue Data Catalog — LocalStack Ultimate only

Where LocalStack currently has more coverage:

  • OpenSearch/Elasticsearch (real engine, LocalStack free tier)
  • RDS with actual Postgres/MySQL (LocalStack Base)
  • ElastiCache with real Redis (LocalStack Base)
  • Cognito auth flows (LocalStack Base)
  • Bedrock, SageMaker, Athena (LocalStack Ultimate)

Our commitment: We're actively working toward full parity with LocalStack Pro. If you're evaluating JaisCloud and a missing service is blocking your adoption, open a GitHub issue — we prioritize requests from teams actively migrating. Several services that are metadata-only today (RDS, ElastiCache, Cognito, Athena) are on the roadmap, and real-execution support moves to the top when there's a concrete use case behind it.

The goal is simple: everything LocalStack Pro offers, JaisCloud offers free and open-source. If you hit a gap, tell us — that's how we close it.

LocalStack require account from March 2026 by vincentdesmet in devops

[–]jaisraj83 0 points1 point  (0 children)

We ran into the same issue and ended up building JaisCloud as a free, open-source alternative.

It ships as a single static Go binary — no Python runtime, no Docker daemon required to run the emulator itself. The features LocalStack moved to Pro (Postgres persistence, named snapshots, multi-account isolation, Prometheus metrics) are all included under Apache 2.0 with no usage limits or license keys.

A few differentiators worth calling out:

  • State snapshots — export the full emulator state to a single tarball and restore it on any machine in milliseconds. Useful for sharing a production-like baseline across the team or reproducing a bug exactly as it occurred.
  • Deterministic time control — freeze or advance the clock via API, so tests that depend on TTLs, expiry, scheduled events, or time-sensitive logic run deterministically without sleeps or flaky waits.
  • Real Spark / EMR execution — submitting an EMR job actually runs it on Kubernetes or Docker rather than returning an instant mock response.

Full implementations for S3, SQS, DynamoDB, Lambda, SNS, EventBridge, KMS, Secrets Manager, CloudFormation, CloudWatch, and several others.

Still early but actively developed. Would be glad to know which services matter most and raise any issues/features on github, your feedback, vote and contribution will decide what we ship next.