Microservices: Know why & Know how
--
As per Moore’s law, the number of transistors on a computer chip was doubling every 18 to 24 months — what would be Moore’s law for the future of Cloud?
We are in a time where code writes itself (eg. Github Copilot AI programming using the world’s advanced AI GPT-3). Mostly we are leading to a phase where repetitive tasks are not worth coding and technologists will have to innovate to create value. Yet, we are in a very interesting time where we are sandwiched between Legacy applications and platforms/products built using ultra-modern technology.
As technology continuously evolves, Software Architecture has been evolving big time.
- Monolithic to
- Service-Oriented Architecture (SOA) to
- Microservices
are a few Software design patterns/architectures we keep discussing.
There have been so many Software Architectural patterns that are ruling over several decades. By implementing Microservices or SOA, we do not stop using any of the below Microservices — we use them in the same way as we have used before.
Few of the core Design patterns
- Multi-tenant architecture (Software-As-A-Service SAAS based)
- Stateless / Stateful architecture design
- N-tier layered architecture
- Circuit breaker architecture
- Serverless Architecture
- Queue based architecture
- Event-Driven architecture
- Cache based architecture
- Bulkheads pattern
- Floating IP pattern
- Container-based application
- Database based application
we shall discuss more in a separate Architecture series. We shall touch base on a few of these patterns as part of the Microservices series where required.
What is Microservices
What if India is one big city-state country without its 28 states and 8 union territories? and what if Singapore has 20 states and is not a city-state country? This statement according to my puts up the uniqueness of Microservices and Monolithic and when to possibly use Microservices and Monolithic.
Coming back to India, given its size and massive population, instead of governing the country as…
