The dawn of observability across the SDLC has fully disrupted standard performance monitoring and management practices. See why.
Apache Kafka: a streaming engine for collecting, caching, and processing high volumes of data in real time. Explore the essentials now.
Stats
Reputation: | 372 |
Pageviews: | 217.7K |
Articles: | 9 |
Comments: | 2 |
Comments
Oct 10, 2019 · Víctor Orozco
It mostly depends on your architecture and application size.
For small applications it is common to do it, but most of the times separating front from backend is a wise option if you want independent releases and management.
For instance, you could pack your entire backend in a given war file and your front-end in a totally different war if using war files is a requirement.
May 01, 2019 · Víctor Orozco
Indeed "use" is a better option to represent the try-with-resources usecase. However I was forced to create a let extension block since DataSource is not autocloseable as required by use, maybe I should state this "simulation" explicitly.
Thanks for your feedback!