modern-web | Progressive Enhancement , Responsive Design , and CSS3 | Style Language library

The Baeldung article Spring Security Authentication Provider has an example that I think suits your needs.

Simply create your own authentication provider that authenticates as you see fit, and then register it in your security configuration.

You use interfaces to be able to change implementations without modifiying your code.

If in a future you use another "way" of sending mails, you just need to change the IMailSender implementation and that's all. Otherwise you would need to refactor all your code depending on your MailSender implementation.

Normally you would use your IMailSender interface also in your validation project. So yes, this intertface should reside in a common library, which will be referenced by both libraries.

Then you will inject (normally via IoC) the implementation in your services, which depend on IMailSender

Usually your Infrastructure library will have have the implementations of your interfaces (some of them may be declared in your "core" library and others...) which will be injected in the classes using it.

So the "infrastructure library" is a way to abstract you implementations, so your code soes not rely on specific classes but on interfaces, being way easier to refactor/change in a future.

There are some other points (it also depends if you are using DDD etc..here every Domain has its own infrastructure) but for me this is the main "reason" of an infrastructure layer.

In this case I would not duplicate the interface, as long as you need the same functionality in both libraries. If not the case, then create two interfaces, each serving the specific needs.

First problem is that Stock was defining two ids (id form AbstractEntity and Ticker) and is not implementing Serializable.

For the second issue...just add this.stockService = stockService in MainView constructor

Solved by adding the following dependency

you added the parentheses for DesiredCapabilities

I don't think that this diagram belongs to any UML type, isn't it?

That does not follow UML notation, for instance as I know the only cases of a rectangle with dotted border are regions(interruptible, expansion) in an activity and your diagram is not at all for an activity.

Does this diagram follow any kind of standard notation?

The more important is not to know if the notation looks like something from UML but to know what is represented.

As the title indicate that diagram shows the architecture, but with mixed types of elements, the closer possible in UML seems to be a deployment diagram, a little bit more far component diagram.

The reason it violates the persistence ignorance principle is very simple: you have to make the properties virtual to make EF happy, so you changed the business code duo to a persistence concern. And besides directly violating the principle, using features of EF that override members of your class change the type of the class, so, for example, in your Equals implementation, you cannot use GetType() anymore to compare the two instances, as the actual type of the object is generated by EF at runtime, so again, you start to change your domain logic according to persistence concerns. On a side note, I would also advise against using EF's lazy loading in most cases, because it only works synchronously, blocking the current thread.

filters.dateFrom is an object, and as your error message explains, objects can't be directly rendered as React children.

Date objects can be rendered as strings though. The simplest case would be something like the following.

You can expand environment variables in .env file. When React app is built, it has access to variables in your Heroku dyno, and react-scripts supports referencing them in your .env file. See more in docs.

With this in mind, your .env file would look like: