Real-Time monitoring package for Laravel VS Vaadin

If you're interested in learning more about Inspector and the other features they offer, I'd definitely recommend checking out their website.

Are you responsible for software development in your company? Consider trying my product Inspector to find out bugs and bottlenecks in your code automatically. Before your customers stumble onto the problem.

inspector.dev - A complete Real-Time monitoring dashboard in less than one minute with free forever tier.

Hi, I'm Valerio, founder and CTO at Inspector.

Today it may not be so easy to navigate the world of monitoring, probably because so many different data can be used in so many different ways. Now I’m the creator and CTO of Inspector, a monitoring platform used by developers in more than ten countries, so in this article I would share my experience working in the monitoring industry trying to help you better understand:

Inspector works with a lightweight software library that you can install in your application like any other dependencies. In case of Laravek you have our official Laravel package at your disposal. Developers are not always comfortable installing and configuring software at the server level, because these installations are out of the software development lifecycle, or are even managed by external teams.

Hi, I'm Valerio, CTO and founder at Inspector. In this article I would talk about the Repository Pattern and how we implemented it in our Laravel application to solve a scalability problem.

But how do we explain the complexity of the current toolset? This is where the Law of the instrument kicks in: "If the only tool you have is a hammer, it is tempting to treat everything as if it were a nail.". Even if JavaScript was born in the web, JavaScript centered frameworks do not fit properly in the web. That is why we have huge bundles of JavaScript, that is why RSC are necessary (things like RSC were already a thing in Vaadin) and that is how JavaScript became the Birmingham screwdriver.

Off-topic but this blog is using https://vaadin.com, that's the first time I am seeing this framework being used!

But there are frameworks like GWT or Vaadin for Java, but none of them really took off afaik, I've never seen a job posting with either of these.

This small tutorial takes 15 minutes from the start to a working demo. We use Picovoice Porcupine Wake Word Engine to enable a Vaadin-based Java web application.

Are you a long-time Java developer using Spring-related tech stack? Vaadin can bring a fresh brief of the air into your daily development routines.

It’s been 7 years since we deployed our first Vaadin app for production. The whole process has been more than interesting. We developed the application according to an analysis (several modules for the agenda in the field of local government) based on a verbal assignment. The customer started testing on our server and after 2 months found only 3 bugs and requested 2 modifications beyond the original brief. Once implemented, we installed it at the customer’s site. The application started for the first time and is still running :-).

> Slightly off topic, but I found JSF the most productive out of any framework.

In my experience, it has been a horrible technology (even when combined with PrimeFaces) for complex functionality.

When you have a page that has a bunch of tabs, which have tables with custom action buttons, row editing, row expansion, as well as composite components, modal dialogs with other tables inside of those, various dropdowns or autocomplete components and so on, it will break in new ways all the time.

Sometimes the wrong row will be selected, even if you give every element a unique ID, sometimes updating a single table row after AJAX will be nigh impossible, other times the back end methods will be called with the wrong parameters, sometimes your composite components will act in weird ways (such as using the button to close a modal dialog doing nothing).

When used on something simple, it's an okay choice, but enterprise codebases that have been developed for years (not even a decade) across multiple versions will rot faster than just having a RESTful API and some separate SPA (that can be thrown out and rewritten altogether, if need be).

Another option in the space is Vaadin which feels okay, but has its own problems: https://vaadin.com/

Of course, my experiences are subjective and my own.

Did you find an excellent custom element that would make sense in your Vaadin Java web application? Maybe that is a web component that you previously published yourself in npmjs.com?