March LiveStream - Implementing NodeJS Observability, PageSpeed perf w/ DataVis
Details
Hi Everyone! Yes, it's been a month and we have some absolutely rocking volunteer speakers to join us for this Livestream :-)
Please join us and get involved with your many questions! Let's have a look at the details below....
RSVP to get your link and subscribe to the BrisJS youtube for Monday!
š¹ Youtube Livestream of the Virtual Event:
If you RSVP to the meetup you'll see the youtube link on this event page (on the right sidebar!), and you can subscribe to the BrisJS youtube channel (https://youtube.com/c/BrisJS/) to get the alert and link of the stream going live š
ā Questions/voting and feedback will be gathered using Slido for Q&A:
https://app.sli.do/event/6kHUdrHVQTGdBJKmS52x6e or use code #222.
I can't overstate enough how grateful I am for those in our wonderful community who get their thinking caps on and contribute a talk of any length to our monthly events. And we need you for the upcoming meetups too! Your talks keep BrisJS alive!
---------------
š Implementing Observability in Node.js - Ashley Davis - 20-30min
After the excellent overview on Observability from Andrei Hawke in February, Ashley has a follow-up talk:
Let's journey with Ashley into implementing Observability in a Node.js microservices project using open telemetry and Honeycomb.
Open telemetry can seem really complicated and overwhelming, but once you know what you need (with a bit of help from Honeycomb's SDK) it's actually quite easy to get a lot just from it just by integrating the Node.js automatic instrumentation.
We'll see how to integrate automatically distributed traces into our Node.js code and then how to find those traces in the Honeycomb UI.
We'll then learn the basics of creating spans, adding attributes and recording events and errors.
š„ļø Achieving Page Speed with a Data-heavy Visualisation (or, Why I hate Tableau) - Murray Bourne - 30-40m
Many data visualisations (in fact, many sites for that matter) suffer from slow load times due to bloated scripts and poor optimisation. This talk demonstrates the possibilities for solving these issues using a case study.
---------------
Thanks everyone for making the effort and marking your diaries!
Lots of opportunities for Q&A through Slido too! Get your thinking caps on and see you on the night!
---------------
ā Why not volunteer to speak next time? We're taking talks anytime! https://brisjs.org/#present for details... or...
š You can check our Github issues page for upcoming topics: https://github.com/BrisJS/meetups/issues
š Submit a new topic with a template: http://tiny.cc/new-brisjs-talk
š Code of Conduct
BrisJS is dedicated to a harassment-free experience for everyone. Our anti-harassment policy can be found at: https://brisjs.org/#conduct
We expect everyone to abide by this straightforward policy to attend in person or interact online.
Please get in touch for presenting your insightful discoveries in the rapidly developing frontend or backend javascript world.
You're also welcome to get in touch with me at kevinv @brisjs.org (or tweet at @brisjs) for any information or future events.