Yelb, yet another sample app
Another pet project I have spent cycles on as of late is an open source sample application called Yelb (thanks to my
partner in crime chief developer Andrea Siviero for initiating me to the mysteries of Angular2).
This is the link to the Yelb repo on GitHub.
I am trying to be fairly verbose in the README files in the repo so I am not going to repeat myself here. Someone said GitHub repos are the new blog posts in the DevOps and cloud era. I couldn’t agree more.
For the records, Yelb looks like this (as of today). The skeleton of this interface was literally stolen (with permission) from a sample application the Clarity team developed.
When deployed with direct Internet access it should allow people to vote and (thanks to Angular2 and the Clarity based UI) you will see graphs dynamically changing. In addition to that, Yelb also track the number of page views as well as the application layer container hostname serving the request.
I thought this was a good mix of features to be able to demo an app to an audience while inspecting what was going on in the app architecture (e.g. watching the container name serving the request changing when multiple containers are deployed in the app server layer).
Good for using it to demo Docker at a conference, good for using it as the basis to build a new deployment YAML for the 37th container orchestration framework we will see next week.
This is the architecture of the application (as of today).
Check on the GitHub repo for more (up to date) information about Yelb.
If you are into the container space I think it helps a lot owning something that you can bring from personal development (from scratch) to production. You have got to see all the problems a dev sees by taking his/her own app into production using containers and frameworks of sort.
While you are more than welcome to use Yelb for your own demos and tests (at your own peril), I truly suggest you build your own Yelb.
Not to mention the amount of things you learn as you go through these exercises. I am going to embarrass myself here by saying I didn’t even know Angular was not server side and that I didn’t know how the mechanics of the Angular compiling process worked. Stack Overflow is such an awesome resource when you are into these things.