Book Image

Learn Java 12 Programming

By : Nick Samoylov
Book Image

Learn Java 12 Programming

By: Nick Samoylov

Overview of this book

Java is one of the preferred languages among developers, used in everything right from smartphones, and game consoles to even supercomputers, and its new features simply add to the richness of the language. This book on Java programming begins by helping you learn how to install the Java Development Kit. You will then focus on understanding object-oriented programming (OOP), with exclusive insights into concepts like abstraction, encapsulation, inheritance, and polymorphism, which will help you when programming for real-world apps. Next, you’ll cover fundamental programming structures of Java such as data structures and algorithms that will serve as the building blocks for your apps. You will also delve into core programming topics that will assist you with error handling, debugging, and testing your apps. As you progress, you’ll move on to advanced topics such as Java libraries, database management, and network programming, which will hone your skills in building professional-grade apps. Further on, you’ll understand how to create a graphic user interface using JavaFX and learn to build scalable apps by taking advantage of reactive and functional programming. By the end of this book, you’ll not only be well versed with Java 10, 11, and 12, but also gain a perspective into the future of this language and software development in general.
Table of Contents (25 chapters)
Free Chapter
Section 1: Overview of Java Programming
Section 2: Building Blocks of Java
Section 3: Advanced Java

The size of a microservice

There is no universal answer to the question How small does a microservice have to be? The general consensus aligns itself with the following characteristics of a microservice (in no particular order):

  • The size of the source code should be smaller than that of the service in SOA architecture.
  • One development team should be able to support several microservices, and the size of the team should be such that two pizzas are enough to provide lunch for the whole team.
  • It has to be deployable and independent of other microservices, assuming there is no change in the contract (that is, the API).
  • Each microservice has to have its own database (or schema, or set of tables, at least) – although, this is a subject of debate, especially in cases where several microservices are able to modify the same dataset; if the same team maintains all of them, it is...