Microservice Architecture & Angel Framework

Hello folks! I’ve spent some time playing around with Dart since my last post and I’ve involved myself in another experiment. This time, I decided to create a Restful API and Server Side APIs using Dart programming language.

For those who don’t know what Dart is, It is a programming language which is easy to learn and is used for building user interface as well as backend API’s. Need more details about dart? click here.

Now, lets directly jump into Microservices.

What is Microservices ?

Microservices has become quite a buzzword in recent days. Theoretically, it is also known as Microservice Architecture. It is an architectural style that structures an application as a collection of services that are:

• Highly maintainable and testable.
• Loosely coupled.
• Independently deployable.
• Organized around business capabilities.
• Owned by a small team.

Best example for microservices architecture is a Security firewall application where we can use this as an independent module in any of our applications. Many businesses face growing infrastructure costs caused by the way their current architecture operates. Making any kind of change to an application in a monolithic architecture can be expensive because every part of the monolith interacts with other parts — so a change in one place affects other aspects. This means a lot more work for developers and operations professionals to sort out the side effects of updates before they can make them. More updates means the bigger the monolith grows and the more time and resources have to go into making future changes.

What is Angel?

Angel is a highly extensible, fully featured server side framework built in Dart. It is designed with extensibility in mind, so even when we need a feature that’s not officially supported, we can easily implement it by creating our own plugin/package. It has first class client support for web, flutter and VM.

It has features like hot reloading, Controllers, Dependency Injection & ORM. It has the direct support for GraphQL, MongoDB & RethinkDB. It also provides support for server-side templating, WebSockets, authentication, and much more.

Request Life Cycle of Angel

Requests in the Angel framework go through a relatively complex lifecycle, and to truly master the framework, one must understand that lifecycle. The complete lifecycle is mentioned below chronologically:

1. startServer is called.
2. Each HttpRequest is sent through handleRequest.
3. handleRequest converts the HttpRequest to a RequestContext, and converts its HttpResponse into a ResponseContext.
4. angel_route is used to match the request path to a list of request handlers.
5. Each handler is executed.
6. If res.isDetached == false, all headers, the status code and the response buffer are sent through the actual HttpResponse.
7. Finally, the HttpResponse is closed.

Middleware of Angel

Sometimes, it's a requirement to recycle code to have it run on multiple routes. Angel allows this in the form of middleware. Middlewares are frequently used as authorization filters or to serialize database data for use in subsequent routes. Middleware in Angel can be any route handler, whether a function or arbitrary data. We can also use middleware to deny/accept request and to throw exceptions.
Here’s an example of how to use a middleware: