You may be a hands-on individual(or a couple/family) running a restaurant business where you take all the decisions or a Vice-president of a large company where you oversee the business but decisions are made by talented middle management that takes responsibility for day-to-day operations.

In either case, it can benefit you (personally as well) and your business if you review your management style and efficiently allocate individual roles for your team or employees.

I like to travel by road. I really do, it allows me to connect to the changes that are taking place physically as one place connects to another and observe the transition in time and space.

Last year, I was on my way to Khajurao from New Delhi, India with 2 of my colleagues (it’s a 600km drive). I noticed that on our way we crossed many industrial towns. One that caught my attention is called Firozabad, a town known for its glass production. …

First, write an overview of the app that you have in mind. Make sure you include key functionalities and who you think would be the captive audience for it.

Decide if it will be a website (mobile or desktop or both) or/and an app.

Think about how the data in the website/ app will be updated. You are likely to require a Content Management System (‘Dashboard’) where you will be updating or reviewing your app performance.

Think of the tentative timeline that you have in mind. Always remember that applications must be tested thoroughly, as unit tests and scenarios tests…

Benefits, Challenges and how Microservices Architecture compares with Monolithic Architectures.

Why? What About Monolithic Architecture?

Here we are, thinking what’s wrong with using Monolithic Architectures? Not much to be honest, and if you haven’t faced any issues with it, you can still read through this article to see where you may face some in the future. There are some limitations that often become the bottleneck in your development process as you scale your application.

But this article is not to say Microservices are the answer to everything. Event-driven architectures have their own pros and cons, and you can read about some of the main ones in my previous article ‘…

Background:

GraphQL is a query language (Graph Query Language) developed by Facebook in 2012 and released publicly in 2015.

3 main characteristics of GraphQL are:

• Clients can specify exactly what data it needs
• Makes it easier to aggregate data from multiple sources
• Uses type system to describe data

The idea behind it was to have a single ‘talented’ endpoint that can handle complex queries instead of multiple endpoints (RestAPI).

Earlier we had SOAP (earlier known as Simple Object Access Protocol). Then came along REST, which gave us a lot more flexibility over SOAP, and it performed well for some time…

Many of the developers that I have interviewed of late speak about their interest in event-driven architecture and how micro-services should be considered for most of our new projects. While I agree with it to some extent, I wanted to share a few challenges that you may encounter if you decide to go ahead.

The following are some good articles that you should read, to really understand how event-driven architecture solves a lot of modern problems.

‘How event-driven architecture solves modern web problems’ by Bogdan Sucaciu: You can read it here.

‘The shift to event-driven evolution, benefits and competitive advantages’…

For this article, I have taken 3 lessons from a book that I read recently that resonated with my past experiences. I enjoy reading business books that teach strategies and management skills. The lessons I am referring to for this article is mostly from:

*Lessons Learned — Straight Talk from the world’s top business leaders — Making Strategies Work

3 simple yet effective lessons for implementing strategies