event-driven-web-components-realworld-example-app

Exemplary real world application built with Vanilla JS Web Components in an Event Driven Architecture (by mits-gossau)
Add to my DEV experience Event event-driven vanilla-javascript vanilla-js Webcomponents eventdriven Architecture Realworld realworld-frontend ES6 usetheplatform
Source Code
mits-gossau.github.io
event-driven-web-components-realworld-example-app Reviews
Suggest alternative
Edit details
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.
www.influxdata.com
Sponsored

Event-driven-web-components-realworld-example-app Alternatives

Similar projects and alternatives to event-driven-web-components-realworld-example-app based on common topics and language

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better event-driven-web-components-realworld-example-app alternative or higher similarity.
Suggest an alternative to event-driven-web-components-realworld-example-app

event-driven-web-components-realworld-example-app reviews and mentions

Posts with mentions or reviews of event-driven-web-components-realworld-example-app. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-07-03.
  • Build an Event Driven TodoMVC App with 8 lightweight VanillaJS Web Components
    5 projects | dev.to | 3 Jul 2021
    Note about Browser compatibility: This example uses the attribute "is", which is not yet supported by IOS. It is possible to simply avoid this problem by wrapping elements with web components. As can be seen at our Real World Example.
  • Web Components and now what?
    2 projects | dev.to | 14 Jun 2021
    An Event Driven Architecture makes stuff like stores obsolete. Your components react on events and if they need something, they emit their event to ask for it. Sure, at this level you are free to decide, if you want to cache certain events, fetches, etc. or if you just want to fire and forget. We chose to simply cancel ongoing fetches at some endpoints (https://github.com/mits-gossau/event-driven-web-components-realworld-example-app/blob/master/src/es/components/controllers/Article.js#L81) but not all those approaches require any difficult logic anymore. Why should you even try to bloat your frontend with a bunch of business logic, if you have an endpoint with that logic already implemented? Keep it simple! 🤯

Stats

Basic event-driven-web-components-realworld-example-app repo stats
2
71
1.4
about 1 year ago

mits-gossau/event-driven-web-components-realworld-example-app is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of event-driven-web-components-realworld-example-app is JavaScript.

Popular Comparisons

  1. event-driven-web-components-realworld-example-app VS todomvc-app-template
  2. event-driven-web-components-realworld-example-app VS kind-stranger
  3. event-driven-web-components-realworld-example-app VS web-components-cms-template
  4. event-driven-web-components-realworld-example-app VS todomvc-app
  5. event-driven-web-components-realworld-example-app VS react-form-debounce

Sponsored
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com