There is a process we need to follow when designing Microservices architecture. We must not forget that designing Microservices architecture should be methodical. The worst thing that can happen when designing Microservices architecture is to rush into development. It should be like “Plan more, Code less”.
The more you plan, the more you think about the overall system mapping, the more you know what you are going into, the less you will code later.
And of course, the less we code, the fewer bugs we create and the less maintenance we have.
Following this process is critical to the project’s…
I will be listing down my articles about K8s best practices here, so we will have one stop place to access all as I write more in future.
More to follow :)…
One of the main reasons to go with Microservices Architecture is to roll out upgrades with minimum to no-impact for the running system and rolling out upgrade more frequently with Agile way. This could be daily or weekly or may be many times per day depending on criticality of the system.
If we are following Microservices guidelines to architecture, we can embark on more agile release management process. Moving release process to Microservices continuous delivery when each service is ready will speed up the things and help to increase scalability and productivity aspect of the development process.
If you are…
There are two main things we talk about when we say this is good code, but before I further discuss, what do you think good code is? Think about that.
OpenStack is an Infrastructure as a service platform that controls large pools of compute, storage and networking resources throughout a data center. All resources are managed through a dashboard (or CLI or API) that gives administration control while empowering their users to provision resources through web interface (or CLI or API).
OpenStack is a global collaboration of developers and cloud computing experts producing open source cloud computing platform for public and private clouds.
The project aims to deliver solutions for all types of clouds by being simple to implement, massively scalable and feature rich.
OpenStack turns all those sets of…
Transitioning to the cloud is one of the most important things happening in IT today.
Let's talk about an organization without cloud computing.
It is a typical organization with a headquarters and some number of branch offices with users in them. Users rely on applications that run directly on the hardware that belongs to their organization.
Probably running in some on-premise data center, those applications could run on bare metal servers or run inside virtual machines. …
Following best practices is very important to make great software. The question is, should we blindly follow them in every project and make things complicated?
Things are changing really fast and even if we spend years to build something, there will be changes to that. The bottom line is we can not really predict the future, so why we need to take care of every possible scenarios and build a software with features that we do not want RIGHT NOW.
The best is to keep things simple (KISS) until “simple” is no longer satisfactory. KISS is not about writing bad…
Lets discuss this in very high-level manner and try to see how these technologies work together. Also lets try to understand what all these cryptic names in the Hadoop ecosystem really mean and what everything is for at a very high level.
Major Components
Lets briefly touch on all these different technologies. We can group them in to three major areas,
- Core Hadoop Ecosystem
- External Data Storage
- Query Engines
Core Hadoop Ecosystem
PINK colored things are part of Hadoop itself. Everything else is soft of add on projects that have come out over time that integrate with it so we can solve specific problems.
One of the most common topics when talking about Microservices is breaking monolith to Microservices. A lot of organizations trying to go this path of converting their existing legacy monolith to modern Microservices system. There are various reasons for such migrations and we have to be prepared for such requests.
Many times organization wants to improve the current system and it believes that migrating to Microservices will do just that. This is not always the case as we have discussed earlier.
If you decided to go with the change, then you must make sure its is thoroughly planned and must…
If you read my previous articles, we have discussed what needed to design a robust, reliable and easy to maintain Microservices architecture. In reality, things are not going in correct way always. Microservices requires thorough design and a lot of the work is happening before writing the first line of code. They are not “Fire and Forget”. You can not just say to the developers that we are going to do Microservices and good luck with that ;).
In-fact, its quite easy to make mistakes that will cause the project to fail. …
Ishan Liyanage
Passionate Technical Lead, Senior Software Developer and free and open source software advocate. Based in Singapore.
