Skip to main content

Posts

Showing posts with the label Solution Architecture

Solution Architecture: 11 Key factors in choosing right technology stack for enterprise applications

Choosing right technology stack! A vital part of creating solution architecture is the selection of technologies for each of the components. As a solution architect, when choosing a technology, you should look at it from an architecture and development perspective as well to build resilence with agile business solutions. One of the hardest things about technology selection is that for every problem there are several technology options and a lot of information available about them. Fortunately, selecting the right technology is not that tricky and you can quickly trim the options down by considering some of the key factors that we are going to see in this post.  This article is of my thought process, and it's a checklist of non-negotiable considerations for choosing a technology stack or a COTS product based on my hands-on experience in designing and executing enterprise scale applications/services, but the list is not limited to, and does not recommend any specific technology/plat...

Microservices: How to choose right API style that fits to your Solution Requirements gRPC over Restful

Hello Welcome to this post!   An effective API design is vital in a Microservices architecture because all data exchange between services happens either through messages or API calls. REST style is probably the most known as it has become common among the Web API. But lately, the gRPC framework is becoming quite popular to build high performance systems. So, you might get these questions when involving in designing an API architecture. In this post , you would be able to find answers and to understand the capabilities of gRPC framework, features of Protobuf and HTTP/2 protocol and finally overview of common use cases of gRPC over REST API. so, let's keep reading further for technical insights. REST: a brief overview Before we start looking into details of the gRPC framework, let’s take a brief overview of RESTful services first. The standard REST methods built on HTTP 1.x. with well-defined status codes help in identifying cause of problems. Generated contracts, m...

Solutions Architecture Interview Questions Part-3

Solutions Architecture Questions 1. How did you manage the app session? Did you consider Azure Redis? 2. What are the anti-patterns that do not fit for cloud computing? 3. One of your customers wants to go for a microservices approach. How do you approach building microservices? 4. How does the microservice approach differ from other architecture? 5. Need to migrate a legacy code to microservices - what are the other frameworks and other things you keep in mind going forward? 6. Creators of microservices added 15 factors application principles/guidelines that your application should be followed. What are those? 7. 8k tables managed under one db with 3 or 4 schemas is like a bad scenario - can you give a data migration strategy? What is your thought process? How do you categorize the data? How do you want to build a tech platform for different data types? 8. Have you got experience with big data?  9. What would be one solution that you have given that helped customers greatly in ter...

Solutions Architecture Interview Questions Part-2

Solutions Architecture Interview Questions Azure Api management - how to enable security? Can we use Azure valut with public and private keys? What are the configuration required in Api management? What are the Api Gateway policies you defined or explained to your engineers? Service bus - How queuing messages is managed? Azure functions - how to secure from public internet access? When do you apply the CQRS pattern? How do you achieve db replication mechanisam? How is replication managed in NOSQL? Have you done micrososervice architecture? How do you enable replication between microservices ? How domain driven design helps designing the microservices? What is the difference between event-driven and event-source? Have you tried the service bus/event grid? How can a .NET app consume a Kakfa event? through polling or receiving? Have you considered logic apps in your solution? Why? Have you done db modeling? What are Power Apps use cases? Solutions Architecture Questions Part-3

Solutions Architecture Interview Questions Part-1

Solutions Architecture Interview Questions Can you talk about your latest solution architecture proposed? How did you approach providing a solution? Why? What are the patterns you followed for the last project? Are they typical web api’s or microservices? What are security design improvements considered while solutioning? How are on-premises and hybrid cloud setup/connectivity done? What are the issues faced? What kind of DR/HA strategy was considered? How about multi-cloud strategy? Was the solution considered the multi-region setup? Can you explain the CI and CD workflow followed? Did you support other teams as well? Stack holder management What is your role, whether you do a solution and leave or would support implementation? Have you done any certifications? Why do you want to change the job? Solutions Architecture Questions Part-2

Software Architectural Terms Explained - Layers vs Tiers With an example

What is the difference between Layers and Tiers? |    Two-tier, Three-tier and N-tier Let's learn in this post with an example. We might heard couple of times but never worried about difference between Layers and Tiers, if somebody asks this question, immediately an engineer may think like this, “ I aware about Two-tier, Three-tier and N-tier also involved in implementation of Presentation Layer, Business Logic layer and Data Access Layer but what are the difference between these terms? Or Are all denotes the same only? ” Being as an application engineer you may need not worry about any architectural terms such as layer, tier etc. However, when you became a senior professional or someone involves in application architecture design and architect activities then you should be very clear on this simple basic things. Alright, let’s start understand what those terms means? and, how each term differs from other one on the application architecture front? For ease of understan...