Moment JS - Some date functions

- 

       


exports.getDateByRange = function(req, options) {

  var start_date = req.param('start_date');
  var end_date = req.param('end_date');
  var date_type = req.param('date_type') || "yesterday_revenue";

  if (date_type == "yesterday_revenue") {

    options.start_date = moment().subtract(1, 'day').startOf('day')._d;
    options.end_date = moment().subtract(1, 'day').startOf('day').add({
      hour: 23,
      minute: 59
    })._d;

  } else if (date_type == "week_to_date_revenue") {

    options.start_date = moment().startOf('week')._d;
    options.end_date = moment()._d;

  } else if (date_type == "month_to_date_revenue") {

    options.start_date = moment().startOf('month')._d;
    options.end_date = moment()._d;


  } else if (date_type == "quarter_to_date_revenue") {

    options.start_date = moment().startOf('quarter')._d;
    options.end_date = moment()._d;

  }

  return options;

}

Comments

Post a Comment

Popular posts from this blog

Design a notification system

-
Image
Design a notification system Functional Requirements Users receive notifications as the events happen within the platform Users can subscribe to a channel to receive all relevant notifications Users can receive notifications in their respective client app (Mobile, web, integrations) Notification can be rate-limited Non-Functional Requirements Always available Easy to add new clients Scalable: Linearly scalable What is the scale of the system? Average of 50k notifications a day  — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —  Could there be Some Questions — Answers? What kind of notifications? Push notification, SMS, EMail What have supported devices? IOS, Android, Laptop / Device Design Constraints Average of 50K notifications a day. Per notification would be 100 chars. Every char 2 Byte. 100 chars X 2 Byte = 200 Byte And we need to store some metadata(Id, user_id, date, device_type etc. ) for notification , and we assume 100 bytes : 200 * 1000 = 20000 bayt 50.000 * 2000
Read more

NETFLIX HIGH-LEVEL SYSTEM DESIGN

-
Image
  STEP - 1 Functional Req   User Registration + login + profiles Search Recommendations Activity tracking Recommendation generation Dashboard Payment Content Ingestion and Delivery Rights + Licences Categorization Notifications Trend Movies Watch History Endorsement Design Constraints Number of users: 100 million Daily active user: %10 Content Upload / sec: Minimal Content Streamed / sec: Need scaling  How many videos let’s say 20000 Averaga per video 10 GB : 3gb HD + 1gb sd = 4 gb.  Avg per video 2,5 hours = 10 GB Content Size: the average size of the video data User activity tracking: High Content streaming latency STEP - 2  Define Microservices We can bucketize functional requirements into Microservices.   The system is a huge system so should be a lot of teams to handle these requirements.  Multiple Microservices - Breadth Oriented System. High Priority Microservices  Microservices  Technology Type User activity tracking MS Simple time-series K-V workload with TTL/count Recommendat
Read more

URL Shortener System Design

-
Image
STEP 1  Functional Req. Given a Long URL, generate a unique short URL. Given a short URL, redirect to a long URL Customized URL,(User should be able to pick a custom short link) TTL (User should be able to specify the expiration time) Non-Functional Req. The system should be highly available. With min latency Non-predictable Analytics Design Constraint Generated per second Length of the short URL,  Let’s start with 7 Char set in the short URL; A-Z, a-z, 0-9 STEP - 2 Microservice Design Decision URL Shortener Microservices All requirements can handle the same team A single microservice - A depth-oriented problem STEP - 3 Drawing logic architecture STEP - 4A  TIERS Default we can multiple every tier 3X  App server tier, In-memory Tier, Storage Tier Data Model Short URL/unique ID, Long URL, TTL, creation time K: Short URL/unique id,  V: Rest of the stuff APIs create(Long URL) -> create(V) read(short URL) -> read(K) Similar to CRUD APIs create (K,V), read(K), update(K,V), delete(K)
Read more