Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note on microservice architecture #2962

Merged
merged 2 commits into from
Nov 14, 2023
Merged

Add note on microservice architecture #2962

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
99e65c7
Add note on microservice architecture
tarekoraby Nov 14, 2023
e87826e
disable HeadingCase Vale rule
jouni Nov 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions articles/lit/start/faq.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ order: 50

= FAQ

pass:[<!-- vale Vaadin.HeadingCase = NO -->]

== What is Hilla?

Hilla is a framework for building reactive web applications on Java backends.
Expand Down Expand Up @@ -104,4 +106,7 @@ Yes. You can use standard Maven modules in your application, or even external de
Hilla is developed using Java as the reference language for the backend. Hilla parses `.class` files, which can be compiled from other languages as well, but support from some features may vary depending on the language.
For example, in Java, an annotation is used to mark a field as not null, while in Kotlin that's part of the language syntax.

== Does Hilla support a microservice architecture?
Yes. Hilla only requires a thin endpoint layer to communicate with the frontend. The rest of the backend can employ a microservice setup that Hilla endpoints would communicate with. See this https://hilla.dev/blog/using-microservices-from-hilla/[blog post] for more details.
tarekoraby marked this conversation as resolved.
Show resolved Hide resolved

// end::content[]