I am starting a new series of blog posts which will cover the ins and outs, tips and tricks of developing web and enterprise applications with Java. Some people refer to enterprise meaning that an application requires interaction with a database and/or communication with other applications and services. Therefore, this blog series will apply to "Web" or "Enterprise" application development for the Java Virtual Machine (JVM) using a number of different technologies.
In this blog series, I will not focus on any single strategy or API, but rather, I will cover a number of technical strategies and options that can be used for developing applications for deployment on the JVM. The main goal is to provide readers with a broad overview of the ecosystem available for the JVM, ensuring that one knows various paths that can be followed to develop sophisticated applications. I also hope to keep each post short and to the point, to allow one more time to develop and experiment, rather than reading my ramblings.
There is no doubt that the JVM is one of the key technologies of our time, as it is installed on millions of devices worldwide, and tens of thousands of applications have been written for the JVM. Even though it is one of the most popular platforms for application development, there tends to be questioning on which path to take when developing certain applications. I like to think of the myriad of options as "tools" that are in the toolshed. We can utilize a Phillips screwdriver to tighten an Allen wrench screw, but it certainly may not be the optimal choice and there are more suitable options available. Much in the same manner, one may use Jakarta EE to develop a microservice just because he or she may know that tech, but there may be better options out there for the particular solution at hand.
Hopefully this blog series will provide you with a better understanding of which tool to choose for your future projects. Just because you know one technology very well, it does not mean that you cannot pick up another technology easily enough and make your toolshed even more substantial for future endeavors. One should continually learn new technologies so that they are not locked into using a single strategy.
To that end...I will start this series by showing how to develop a very simple web service which will be used to provide a temperature reading. The web service end point can be harnessed by clients to obtain the current temperature by reading a file that has been written by a temperature sensor connected to a raspberry pi. In the first post, I will utilize Jakarta EE 8 to build this service.
Note: As you read on in this series, you will see that version numbers of APIs mean the world. As with any technology, web and enterprise development are ever-changing, and so moving from one version to the next usually means that there may be a number of changes in the way a service or application needs to be developed.
The following index will be updated to include posts as they are written for inclusion in this series.
No comments:
Post a Comment
Please leave a comment...