Maximize channel loyalty &amp; engage partners with our top-rated loyalty &amp; rebate software. Customize your Channel Partner Program for effective partner rewards. Learn more.

Channel Loyalty Program | Loyalty Management Software - O4S

O4S is a technology platform that helps distribution-led companies target and incentivize high-performance channel partners to drive sales.

O4S - Crunchbase Company Profile & Funding

O4S | 5,986 followers on LinkedIn. 🚀 Empowering Channels, Accelerating Growth 🚀 | O4S is the operating system for channel growth. 🎯 We are a SaaS platform that helps consumer brands optimize their distribution channels through targeted incentives and loyalty programs.

O4S | LinkedIn

Information on valuation, funding, cap tables, investors, and executives for O4S. Use the PitchBook Platform to explore the full profile.

O4S Company Profile: Valuation & Investors | PitchBook

&quot;O4S redefines how companies engage with their channel partners. Our technology spans 14+ countries, managing channel incentives for 500,000+ partners and serving renowned brands like AkzoNobel, Honeywell, Coca-Cola, Polycab, &amp; Mahindra.\n\nDuring FY23, we managed over $25 Million in payments.

O4S Company Profile, information, investors, valuation & Funding

O4S - Cloud based solutions for targeting and incentivizing channel partners to enable sales. Raised a total funding of $10.1M over 7 rounds from 36 investors. Valued at $31.4M. Founded by Divay Kumar and Shreyans Sipani in the year 2017. O4S has 899 competitors.

O4S - Company Profile - Tracxn

O4S has 5 employees at their 1 location and $2.5 m in total funding,. See insights on O4S including office locations, competitors, revenue, financials, executives, subsidiaries and more at Craft.

O4S Company Profile - Office Locations, Competitors, Revenue, ...

O4S (Original4Sure) on the 2020 30 Under 30 - Asia - Enterprise Technology - Divay Kumar and Shreyans Sipani are cofounders of O4S, an SaaS startup helping

O4S (Original4Sure)

​​The IoT and SaaS-driven platform helps manufacturing companies to digitize and automate the supply chain.

o4s: Supply chain SaaS company O4S raises $6 million - The Economic ...

The O4 Company identifies, creates, develops and commercialises opportunities in the world of media. Harnessing both the online and offline worlds, we aim to disrupt the current business models and create value + for our clients.

Home | O4

O4S, saas helps fmcg, agri and pharmaceutical companies provide end-to-end downstream supply chain visibility. Here you&#x27;ll find information about their funding, investors and team.

O4S company information, funding & investors | Dealroom.co

O4S is hiring - see 8 jobs. At O4S, we are working towards revolutionizing the manner in which business process work across an enterprise’s supply chain, through our pioneer solutions, Original4SureTM &amp; SupplyticsTM. Original4Sure We can all recall instances when we were offered Aquifina/Bislery ...

O4S Jobs | AngelList Talent

O4S SaaS helps Consumer Brands to Digitize and Automate their Supply Chain thereby increasing Sales and Performance.

O4S - Funding, Financials, Valuation & Investors

O4S is a SaaS platform to provide Supply Chain Automation for Manufacturing Companies. Know about O4S company, founders, funding, &amp; Business.

O4S SaaS Platform | Founders | Funding | Business Model

AI \u0026 SaaS-driven platform helps consumer brands to digitize \u0026 automate the supply chain

Interceptors in Spring are used to intercept client requests or responses before they are handled by the controller or before the response is sent back to the client. Interceptors are part of the Spring Web MVC framework and provide a way to add pre/post- processing logic to your application's request-response lifecycle. Realtime Use Cases of Interceptors Some of the the common use cases for interceptors include tasks, such as: Interceptors can be used to log HTTP requests and responses. This can be useful for debugging or tracking the performance of an application. Logging: Interceptors can be used to enforce security policies. For example, an interceptor could be used to check that a user is authenticated before allowing them to access a resource. Security: Interceptors can be used to cache HTTP requests and responses. This can improve the performance of an application by reducing the number of times that requests need to be made to the underlying resources. Caching: Interceptors can be used to transform HTTP requests and responses. For example, an interceptor could be used to convert requests to XML responses. Transformation: JSON Spring Request Life-Cycle In a typical application flow, when the client sends an HTTP request to a specific endpoint(URL), the request is first received by the web server (e.g., Apache Tomcat or Jetty) and then forwarded to the Spring Boot application. Spring Boot The Dispatcher Servlet is the entry point for incoming requests in the Spring Boot application. Once the DispatcherServlet receives the request, it consults the HandlerMapping. The HandlerMapping is responsible for determining which controller should process the incoming request based on the URL mapping defined within your controller. Creating Interceptor in Spring Boot To create an interceptor in Spring Boot, you typically create a class that implements the interface. HandlerInterceptor The interface has three methods: HandlerInterceptor : The preHandle() method is the most important method in the HandlerInterceptor. This method is executed before the actual controller method is called. It returns a boolean value indicating whether the request should continue to the controller or be stopped. preHandle() : This method is executed after the controller method is called but before the response is sent to the client. It allows you to modify the model and view before rendering the response. You can use this method to perform any tasks that you need to do after the request has been handled. For example, you could use the method to add additional information to the response, or to log the response. postHandle() postHandle() : This method is executed after the response has been sent to the client. This method is called even if an exception was thrown during the processing of the request. It's useful for cleanup or resource release tasks. afterCompletion() Interceptor to Check Basic Authentication Let us now create an interceptor to perform the basic authentication check. This interceptor will be invoked only for a specific endpoint. It will do the basic authentication check before allowing access to the controller. /products/new For this example, we will hardcode a username and password to verify the credentials passed by the user. import lombok.extern.slf4j.Slf4j;
import org.springframework.web.servlet.HandlerInterceptor;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.nio.charset.StandardCharsets;
import java.util.Base64;

@Slf4j
public class BasicAuthInterceptor implements HandlerInterceptor {
    private static final String USERNAME = "admin";
    private static final String PASSWORD = "admin";

    @Override
    public boolean preHandle(HttpServletRequest request, HttpServletResponse response, Object handler) throws Exception {
        log.info("BasicAuthInterceptor::preHandle()");

        String authHeader = request.getHeader("Authorization");
        if (authHeader != null && authHeader.startsWith("Basic ")) {

            String base64Credentials = authHeader.substring("Basic ".length());
            byte[] decodedCredentials = Base64.getDecoder().decode(base64Credentials);
            String credentials = new String(decodedCredentials, StandardCharsets.UTF_8);

            String[] parts = credentials.split(":");
            String username = parts[0];
            String password = parts[1];

            if (USERNAME.equals(username) && PASSWORD.equals(password)) {
                return true;
            }
        }

        response.sendError(HttpServletResponse.SC_UNAUTHORIZED, "Unauthorized");
        return false;
    }

    @Override
    public void postHandle(HttpServletRequest request, HttpServletResponse response, Object handler, ModelAndView modelAndView) throws Exception {
        log.info("BasicAuthInterceptor::postHandle()");
    }

    @Override
    public void afterCompletion(HttpServletRequest request, HttpServletResponse response, Object handler, Exception ex) throws Exception {
        log.info("BasicAuthInterceptor::afterCompletion()");
    }
} Enter fullscreen mode Exit fullscreen mode Registering Interceptor in Spring Boot Once you have created your custom interceptor, you need to register it with the Spring Boot application using configuration: WebMvcConfigurer import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.config.annotation.InterceptorRegistry;
import org.springframework.web.servlet.config.annotation.WebMvcConfigurer;

@Configuration
public class WebConfig implements WebMvcConfigurer {

    @Override
    public void addInterceptors(InterceptorRegistry registry) {
        registry.addInterceptor(new BasicAuthInterceptor())
                .addPathPatterns("/products/new");
    }
} Learn more about using interceptors with this video: https://youtu.be/DuMf8Nwb-9w?embedable=true This tutorial is first published on . stacktips.com The lead image for this article was generated by HackerNoon's AI Image Generator via the prompt "a screen displaying a website’s backend”. If you like this article, follow me on Twitter or check out my Youtube channel for more such content. @ask_nilan @TheTechMojo Happy learning!

How to Intercept HTTP Request Response in Spring Boot

How to Change Django Code during Seamless Deployment to Production Server Depending on the environment, working with Django is not always as easy as it is shown in tutorials. It may seem simple – if you need to add a column, add a field to a model, create a migration, run it and the column is ready. And, if you need to delete it, then everything is just as simple: delete the field, create a migration, run it and it is done. However, it does not always work that way in production. When you have several servers or containers running on Prod, and migrations are published before the code is published, then it becomes important not to break the seamless deployment. That is, you need to maintain the consistency of a database and code, and even more. In a previous article, I wrote about . Let's move on to the details. how to deploy Django model changes to Production Deleting Column on Production Depending on the deployment architecture, to delete a column on production, you can use several methods. Performing migrations after deploying the code to all pods in one deployment. Performing migrations with the second deployment, immediately after the first one in which the code was deployed. Performing migrations with a separate deployment after deploying the code but with a possible delay and even other deployments. And now, let us look at this in more detail. Let us take the Airport list model as an example. class Airport(models.Model):
    iata = models.CharField(max_length=3, unique=True)
    name = models.CharField(max_length=30, unique=True) If you delete the ‘name’ column from the model and do not create or perform migrations, nothing bad will happen. But if you try to start creating migrations, a migration will be added with the removal of this field: python manage.py makemigrations Nevertheless, keeping an extra unused field in a database is not the best idea.
Therefore, it seems logical to create a migration and then execute it, thereby removing this field from the table in the database. As a result, a test on a local machine shows that everything is working. But when we started to deploy to Prod, a bunch of errors appears. So, everything is different on Prod. When pods with new code are deployed, the following most often happens. Initialization is performed before each deployment, which includes the execution of migrations: python manage.py migrate After that, pods are created, one at a time. Once a pod is created, one of the old pods is destroyed. Now imagine that the migrations have been completed, but the old code is still working. And it will keep working for a while depending on the number and complexity of pods, sometimes for a few seconds, and sometimes for a few minutes or even tens of minutes. So, after the migration is completed, until the replacement of the last pod, almost any request to the Airport model will throw an exception. For example: Airport.objects.first() will throw an exception like: ProgrammingError: column avia_airport.name does not exist
LINE 1: SELECT "avia_airport"."id", "avia_airport"."iata", "avia_airport"."name" Solutions The first solution suggests that you have two types of migration: the one performed before the code is deployed and the one performed after that. If you have this in , then everything is simple. Adding a column, creating a model, and so on must be done before deployment, and deleting must be performed after that. CI / CD The second solution is only possible if you are completely sure that you can perform two deployments in a row without a break and during this time, no one will deploy or change anything. Then you create a migration as usual. After that, you first deploy only code, and then you run the migration. The model class for the previous two methods will look as follows: class Airport(models.Model):
    iata = models.CharField(max_length=3, unique=True) And the migration will look as follows: migrations.RemoveField(
    model_name='avia_airport',
    name='name',
) And  finally, the third solution is for those cases where you cannot guarantee that two versions will be deployed in a row without any interference. In this case, you need to create a "fake" migration. For this, state_operations is used. For example: migrations.RunSQL(
    sql=migrations.RunSQL.noop, 
    reverse_sql=migrations.RunSQL.noop, 
    state_operations=[
        migrations.RemoveField(
            model_name='avia_airport',
            name='name',
        ),
    ]
) This way you inform Django that this migration is completed. And when you run the command, Django will not add the migration with the 'name' field deletion. However, this migration will not delete this field from the table in the database. So, your first deployment will contain the removal of the field from the model in the code and the ‘fake’ migration. makemigrations Then, the second deployment will have to contain the column removal code. But since Django thinks the column was removed in the previous migration, it will have to be deleted using SQL commands. migrations.RunSQL(
    sql="ALTER TABLE public.avia_airport DROP COLUMN name CASCADE",
    reverse_sql=migrations.RunSQL.noop
) If you are not sure what to write in SQL, then create an original migration and run the command: sqlmigrate python manage.py sqlmigrate avia You will see the needed SQL command which you can copy. By the way, I highly recommend specifying in every manual migration. If you have a specific migration rollback script, then should run it. If you do not have it, then use for the migration or for migrations – an empty migration. This will help avoid an exception in case you need to roll back the migration. reverse_sql reverse_sql migrations.RunSQL.noop RunSQL migrations.RunPython.noop RunPython Conclusion Always keep in mind that there are several Django instances running on production, which are updated to a new version sequentially. Also, remember that there is a period of time between performing a migration and updating the code in which users can see an error. This can cause reputational and financial damage. Therefore, use multi-step deployments when changing the database.

Deleting a Column from a Django Model on Production

The Strange Case Of Dr. Jekyll And Mr. Hyde by Robert Louis Stevenson is part of HackerNoon’s Book Blog Post series. You can jump to any chapter in this book here . Chapter VII: Incident at the window CHAPTER VII. INCIDENT AT THE WINDOW It chanced on Sunday, when Mr. Utterson was on his usual walk with Mr. Enfield, that their way lay once again through the by-street; and that when they came in front of the door, both stopped to gaze on it. “Well,” said Enfield, “that story’s at an end at least. We shall never see more of Mr. Hyde.” “I hope not,” said Utterson. “Did I ever tell you that I once saw him, and shared your feeling of repulsion?” “It was impossible to do the one without the other,” returned Enfield. “And by the way, what an ass you must have thought me, not to know that this was a back way to Dr. Jekyll’s! It was partly your own fault that I found it out, even when I did.” “So you found it out, did you?” said Utterson. “But if that be so, we may step into the court and take a look at the windows. To tell you the truth, I am uneasy about poor Jekyll; and even outside, I feel as if the presence of a friend might do him good.” The court was very cool and a little damp, and full of premature twilight, although the sky, high up overhead, was still bright with sunset. The middle one of the three windows was half-way open; and sitting close beside it, taking the air with an infinite sadness of mien, like some disconsolate prisoner, Utterson saw Dr. Jekyll. “What! Jekyll!” he cried. “I trust you are better.” “I am very low, Utterson,” replied the doctor drearily, “very low. It will not last long, thank God.” “You stay too much indoors,” said the lawyer. “You should be out, whipping up the circulation like Mr. Enfield and me. (This is my cousin—Mr. Enfield—Dr. Jekyll.) Come now; get your hat and take a quick turn with us.” “You are very good,” sighed the other. “I should like to very much; but no, no, no, it is quite impossible; I dare not. But indeed, Utterson, I am very glad to see you; this is really a great pleasure; I would ask you and Mr. Enfield up, but the place is really not fit.” “Why, then,” said the lawyer, good-naturedly, “the best thing we can do is to stay down here and speak with you from where we are.” “That is just what I was about to venture to propose,” returned the doctor with a smile. But the words were hardly uttered, before the smile was struck out of his face and succeeded by an expression of such abject terror and despair, as froze the very blood of the two gentlemen below. They saw it but for a glimpse for the window was instantly thrust down; but that glimpse had been sufficient, and they turned and left the court without a word. In silence, too, they traversed the by-street; and it was not until they had come into a neighbouring thoroughfare, where even upon a Sunday there were still some stirrings of life, that Mr. Utterson at last turned and looked at his companion. They were both pale; and there was an answering horror in their eyes. “God forgive us, God forgive us,” said Mr. Utterson. But Mr. Enfield only nodded his head very seriously, and walked on once more in silence. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Stevenson, Robert Louis, 1992. The Strange Case Of Dr. Jekyll And Mr. Hyde. Urbana, Illinois: Project Gutenberg. Retrieved May 2022 from https://www.gutenberg.org/files/43/43-h/43-h.htm#chap07 This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org, located at https://www.gutenberg.org/policy/license.html.

The Strange Case Of Dr. Jekyll And Mr. Hyde: Chapter VII - Incident at the window

When it comes to JavaScript, a promise that is fulfilled is said to be while that that is broken is said to be . Promises replaced callback functions that were used to handle asynchronous operations. resolved rejected Asynchronous operations required multiple callbacks and these would make code unmanageable. Luckily, JavaScript introduced promises natively in ES6 saving us the callback hell. Promises When I started working on JavaScript, some of the articles suggested that JavaScript is an asynchronous language while others stated that it was synchronous. This really frustrated me. I will just save you this frustration by telling you that “JavaScript is an asynchronous programming language”. And with callback functions, we can make it function like Asynchronous programming language. : noun: Assurance that one will do something or that a particular thing will happen. A promise A promise is an object which can be returned synchronously from an asynchronous function. It is returned in one of these possible states: Not yet fulfilled or rejected Pending: This will be called when a promise is fulfilled if Resolved: resolve() This will be called when a promise is not fulfilled for example if is called. Rejected: reject() Prototypes As we saw earlier, a promise has three methods. When a promise is created, it is in a One or more of the three methods will be run when a promise is settled based on whether a promise is or Pending state. fulfilled rejected. .prototype.catch(onRejected) .prototype.then(onFulfilled, onRejected) .prototype.finally(onFinally) Promise Promise Promise The below image shows the flow for and methods. They are chained as shown in the diagram since they return a promise. If (. ) is declared for a promise, then it will be executed whenever a promise is irrespective of whether it is fulfilled or rejected. .then .catch finally settled Flow for .then and .catch methods A practical example of how promises work The ES6 promise constructor takes a function. That function takes two parameters, and . Let’s look at this scenario to better understand promises. resolve() reject() A daughter asks her mother for money to go to a beach party with her friends. The mother tells her she does not have enough money for the trip but she was expecting Molly (One of her friends)to pay back the money she had lent her. Let’s use JavaScript to see how this promise is executed. MumsPromise = ( {
  MumsSavings = ;
  TripExpense = ; (MumsSavings > TripExpense) {
    resolve({ : , : });
  } {
    reject( );
  }
});
MumsPromise.then( { .log( , .stringify(value));
});
MumsPromise.catch( { .log( , reason);
});
MumsPromise.finally( { .log( );
}); let new Promise ( ) function resolve, reject 600 900 if Day "Saturday" Time "11:00 am- 6:30 pm" else "We do not have enough savings" ( ) function value console "Yay! The party is on, Mum already got me a ticket!" JSON ( ) function reason console "Mom coudn't buy me the ticket because " ( ) function console "I know Mum cannever fail to buy me a ticket if she has the money" The output of this code will be Case1 Let’s assume Molly had paid the 600 money that she owed to the mother, then her mother’s savings would now be 1200 money. Case2 In case1, the promise is rejected because the mother is 300 cash short while in case2, the promise is resolved and the daughter goes to the beach party. Promise Chaining Because always returns a new promise, it’s possible to chain promises with precise control over how and where errors are handled. Promises allow you to mimic normal synchronous code’s behaviour. .then() try/catch Like synchronous code, chaining will result in a sequence that runs in serial. In other words, you can do: fetch(url)
  .then(process)
  .then(save)
  .catch(handleErrors)
; Our JavaScript code would them become; MumsPromise = ( {
  MumsSavings = ;
  TripExpense = ; (MumsSavings > TripExpense) {
    resolve({ : , : });
  } {
    reject( );
  }
});
MumsPromise.then( { .log( , .stringify(value));
  }, { .log( , reason);
  }
); let new Promise ( ) function resolve, reject 600 900 if Day "Saturday" Time "11:00 am- 6:30 pm" else "We do not have enough savings" ( ) function value console "Hurray I got this phone as a gift " JSON ( ) function reason console "Mom coudn't buy me the phone because " Important things to note A pending promise may transition into a fulfilled or rejected state. A fulfilled or rejected promise once settled must not transition into any other state. A promise or “thenable” is an object that supplies a standard-compliant method. .then() Once a promise is settled, it must have a value (which can be ) and that value must not change. undefined I hope I kept my promise and you now know what promises are to begin working with them. Add your comments and let me know where I can make some improvements. Follow me on , , Twitter Facebook LinkedIn Also published on Medium's subdomain .

O4S

o4s.io

-- employees

Since n.d.

COMPANY RANKING

O4S

EVERGREEN INDEX #7902

Representing this company? Click here to claim and customize this page!

O4S WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

O4S