print-ms's Introduction

👋 Hi there I'm Abhishek Saxena

I am a Mobile Full Stack Developer with 2 years of experience with expertise in Native Android and Spring Boot.

🛠 Frameworks

🛠 Programming Languages & Tools

🤝🏻 Connect With Me

📖 Recent Articles (View All)

Title	Published In	Featured In
Builder Design Pattern In Kotlin
Jetpack Compose Migration: Best Practices and Strategies
SOLID Design Principles in Kotlin
Strategy Design Pattern In Kotlin
Conditionals, An Easier Design Decision But A Poor Choice
Easily manage image type with sealed classes		-

⚙️ GitHub Analytics

Thanks for stopping by and don't forget to check out my pinned repositories and open sourced projects.

print-ms's People

Contributors

Watchers

print-ms's Issues

Improve printer status api response time

Currently the response can take upto 5s per request.

Should be able to send specs for printing.

Specs

Coloured/Black&White
Copies

Rename global ExceptionHandler to ResourceAdvice

Return whether the printer status with the list of printers

The printer object should also contain information about the printer's status, whether online or offline.

Only respond with success status only if the print request is added to the queue

Manage gradle dependencies with catalog

Add facade layer between presentation and service layer

Experimental Feature

The Resource layer will send/receive DTOs to the *Facade. The facade will take care of the mapping of DTOs to/from Entities. This way the services will not care about the mapping of the data returned by them.

Also, the services will be able to directly communicate with each other without the additional mapping of the data.

Constraint: The service will only interact with the *Facade and the *Resource will only interact with the *Facade.

Possible issue: There will be times wherein the facade will not do much but only act as a bridge between the two layers. It is okay and we should follow the pattern even then as this empty facade will be there for consistency.