DEV Community

Ido Shamun
Ido Shamun

Posted on • Originally published at blog.elegantmonkeys.com

4 1

My Microservices Stack

Here is my some what opinionated stack for building resilient and elastic distributed system. I describe each framework or platform with a single marketing line followed by how I use it.

  • Node.js — A Javascript runtime built on Chrome’s V8 JavaScript engine. Used to build stateless API and automation scripts. Usually my “go-to” language for everything unless heavy lifting is needed.
  • Lagom — An open source framework for building reactive systems in Java or Scala. Used to build systems and API based on Event Sourcing & CQRS.
  • Akka — An open source toolkit for building highly concurrent, distributed and resilient message-driven applications for Java and Scala. Used to build data processing and complex processed based on the Actor Model.
  • PostgreSQL — World’s most advanced open source relational database. Usually my “go-to” database as it fits most of the use cases and most cloud services provide it as a service.
  • Docker — An open platform build, ship, and run distributed applications, whether on laptops, data center VMs, or the cloud. Used to package the applications in a uniform and immutable regardless the language or framework inside.
  • Kubernetes — An open-source system for automating deployment, scaling, and management of containerized applications. Nothing more to say, just the perfect solution for deployment and application orchestration.
  • Google Cloud Platform — Build, innovate, and scale. It simply provides everything I need for running my applications. Kuberenetes, Postgres, Docker registry and much more as a service with no ops needed (just your credit card, of course :P)

Looking forward to see your stack and comments!

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed
  • 2:34 --only-changed
  • 4:27 --repeat-each
  • 5:15 --forbid-only
  • 5:51 --ui --headed --workers 1

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video 📹️

Top comments (0)

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed: Zero in on just the tests that failed in your previous run
  • 2:34 --only-changed: Test only the spec files you've modified in git
  • 4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
  • 5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
  • 5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video 📹️

👋 Kindness is contagious

Engage with a wealth of insights in this thoughtful article, valued within the supportive DEV Community. Coders of every background are welcome to join in and add to our collective wisdom.

A sincere "thank you" often brightens someone’s day. Share your gratitude in the comments below!

On DEV, the act of sharing knowledge eases our journey and fortifies our community ties. Found value in this? A quick thank you to the author can make a significant impact.

Okay