Blog Archives
1 2

01: Q13 “12 Rules” for REST API design & development

These are more like rules to develop RESTFul web services as opposed to being the best practices. REST is an architectural style without any contracts or specifications. So, it is imperative to apply the following rules for better REST API design. #1. Write stateless RESTFul services This means each request…

Read more ...


02: Microservices Architecture design patterns & considerations interview Q&As – Part 1

This extends 10+ Key Microservices Interview Questions Answered. The architects & developers need to know these microservices design patterns & these are best practices to build robust systems. Q1. Why do we need design patterns for Microservices? A1. The goal of microservices is to increase the velocity of application releases,…

Read more ...


02: Scenarios based Java OO concepts & GoF design patterns – naive Template Method pattern

Scenarios based Java OO concepts & GoF design patterns

Read more ...


03: Microservices Architecture design patterns & considerations interview Q&As – Part 2

This extends 02: Microservices Architecture design patterns & considerations interview Q&As – Part 1. 3. Decomposition Design Patterns When decomposing the Microservices, we should avoid having tight coupling between the services. This can be achieved by duplicating the data in the required/dependent services. If you are not duplicating the data…

Read more ...


03: Scenarios based Java OO concepts & GoF design patterns – Strategy Pattern

The following post improves on the design flaws listed in the previous post entitled 02: Scenarios based Java OO design & GoF design patterns – naive Template Method pattern. Scenario: A company named XYZ Retail is in the business of selling Books, CDs and Cosmetics. Books are sales tax exempt…

Read more ...


04: Microservices Architecture design patterns & considerations interview Q&As – Part 3

This extends 03: Microservices Architecture design patterns & considerations interview Q&As – Part 2. 4. Cross-cutting concern patterns Microservices require various cross-cutting concerns such as metrics, reporting exceptions to an exception tracker, logging, distributed tracing, health checks, externalized configuration, and security. Additionally, a service may need to handle service discovery…

Read more ...


05: Microservices Architecture design patterns & considerations interview Q&As – Part 4

This extends 04: Microservices Architecture design patterns & considerations interview Q&As – Part 3. 4. Observability patterns Microservices require various cross-cutting concerns such as metrics, reporting exceptions to an exception tracker, logging, distributed tracing, health checks, externalised configuration, and security. Additionally, a service may need to handle service discovery and…

Read more ...


06: Web design patterns MVC2, MVP, MVVM & MVW

Q1. What’s wrong with Servlets? What is a JSP? What is it used for? What do you know about model 0 (aka MVC0), model 1 (aka MVC1) and model 2 (aka MVC2) patterns? In “model 2” architecture, if you set a request attribute in your JSP, would you be able…

Read more ...
Tags:

06: Microservices Architecture design patterns & considerations interview Q&As – Part 5

This extends 05: Microservices Architecture design patterns & considerations interview Q&As – Part 4. 5. Deployment patterns Microservices enable your development team to roll out software solutions more quickly and better react to customer needs. Microservices deployment patterns or considerations enable easy deployments and allow you to modify microservices. Problem…

Read more ...


12 Java design patterns interview Q&As

Q1. Why use design patterns? A1. 1) Capture design experience from the past: E.g. Facade and value object patterns evolved from performance problems experienced due to multiple remote calls. 2) Promote reuse without having to reinvent the wheel: E.g. The flyweight pattern improves application performance through object reuse, which minimizes…

Read more ...


1 2

Java Developer & Architect Interview Q&As

Java & Big Data Tutorials

Prepare to fast-track & go places

FAQs are marked with 🔥 as some questions are not only more popular with the interviewers, but also required to build robust systems. If you are an interviewer, cover well rounded topics to judge real experience.

Don't be overwhelmed by the number of questions as the technology stacks are so vast. The quality of the answers you provide to some of the key technical & open-ended questions along with your soft skills & attitude will go a long way in getting the job offers.

Note: Some Q&As belong to more than one category.
Top