What is an Embedded Server?


In this article, we focus in exploring what an embedded server is, and how they help make application deployment simpler.

You will Learn

  • What Is An Embedded Server?
  • Why should you use an Embedded Server?
  • How do Embedded Server help with simplifying deployment?

Java Programmer Essentials

As we go towards microservices architectures, what should a Java Programmer learn?

This is the fifth article in series of six articles on Java Programmer Essentials :

Why We Need An Embedded Server?

In a typical microservice architecture, there could be hundreds of microservice instances deployed at a given point in time.

We would like to automate development and deployment of microservices to the maximum extent possible.

A good approach would be to take the application, wrap it in a container image, and manage it as needed using something like Kubernetes.

For this, the deployment process needs to be very simple.

If you are using a custom version of Tomcat, or WebLogic to deploy your application, then you would need to

  • Install Java
  • Install Web Server
  • Deploy application artififact to web server

How can we make it simpler?

An interesting approach would be to make the server a part of your application. In that case, there are just two steps: install the right version of Java, and run the application.

This is where the concept of an embedded server comes in.

What Is An Embedded Server?

An embedded server is embedded as part of the deployable application.

If we talk about Java applications, that would be a JAR.

The advantage with this is you don’t need the server pre-installed in the deployment environment.

With SpringBoot, the default embedded server is Tomcat. Other options available are Jetty and UnderTow.

A lot of developers used to working with WAR and EAR files tend to assume that using an embedded server in a JAR is not stable.

Embedded servers are quite scalable, and can host applications that support millions of users. These are no less scalable than the conventional fat servers.

Switching To Jetty

By default, the Spring Boot framework uses Tomcat as the embedded server of choice. However, you could override this default setting by specifying certain configuration settings. For instance, if you want to use a Jetty dependency instead, then use an <exclusion> element in the XML configuration file, and specify a <dependency> element as well:

image info

A similar dependency also exists for Undertow.

Embedded Servers Have High Utility

As a concept, embedded servers might take some time to get used to. These can be used with applications for deployment in high-workload environments, without sacrificing any reliability or stability.

Embedded servers are also quite lightweight. If you look at a conventional WebSphere or Weblogic installation, or even a default Tomcat setup, their install sizes are huge!

Embedded server images don’t generally result in huge archive sizes and helps in building smaller containers.

Do check out our video on this:

image info

Summary

In this article, we talked about the need for embedded servers as a concept. We discussed how an embedded server works, and how it sits inside an application image. We also saw an example with the Spring Boot framework, which uses Tomcat by default, as the embedded server.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?