Oresztesz Margaritisz

CORE

Chief Software Engineer at EPAM Systems

Company website: https://www.epam.com/

Budapest, HU

Joined Dec 2015

https://twitter.com/gitaroktato

About

Currently working at EPAM as a Chief Software Engineer. Mostly interested in Java, NoSQL, DevOps and Continuous Delivery.

Stats

Reputation:	528
Pageviews:	80.2K
Articles:	7
Comments:	1

Articles
Comments

Articles

Queuing Theory for Software Engineers

In this article, learn the basics of queuing theory that are required for high-level capacity estimations and workload optimization.

June 4, 2024

· 4,230 Views · 4 Likes

Protect Your Invariants!

This tutorial shows you how to handle constraints and validation inside your application. Read below to find out how this way can help you!

January 7, 2022

· 6,662 Views · 32 Likes

An Overview of Health Check Patterns

In this article, I'm going to go through each type of health check and investigate what kind of issues can be resolved with each of them.

July 8, 2020

· 21,177 Views · 12 Likes

Incorporating Fault-Tolerance Into Your Microservice Architecture

In this article, we discuss the process of incorporating fault-tolerance into a microservice architecture.

February 19, 2020

· 9,523 Views · 13 Likes

Designing Fault-Tolerant Microservices With Toxiproxy and Cucumber

Find out how!

October 10, 2019

· 10,323 Views · 2 Likes

Google Authentication for Your AWS Management Console With OAuth 2.0

Learn how to deploy an alternative sign-in mechanism for AWS management console that's using Google accounts for authentication.

May 28, 2018

· 14,361 Views · 9 Likes

Multi-Tenant Cassandra Clusters With Spring Data Cassandra

What options does Cassandra provide for operating multi-tenant clusters? Do you have your services prepared to do the work properly? Read on to find out.

December 4, 2017

· 13,927 Views · 4 Likes

Comments

Google Authentication for Your AWS Management Console With OAuth 2.0

Jul 04, 2018 · Oresztesz Margaritisz

Open the developer toolbar in your browser and check the JavaScript console and the "Network" tab for errors. You should see 3 request-response pairs in the network tab before the redirect happens. These are highlighted as steps 2-4 in the authentication flow diagram. If anything goes wrong, you should see a related error message in the JavaScript console or in the HTTP response. Without seeing what went wrong it's hard to tell more.