Giter Club home page Giter Club logo

hei-admin-api's Introduction

hei-admin-api's People

Contributors

dinasoa avatar haritianaadriano avatar hei-ryan avatar hei-teacher avatar heiherilala avatar iandrianina avatar iloniavo avatar mahefaa avatar onitsiky avatar sanmandresy avatar tanjonaaa avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

hei-admin-api's Issues

Filter users

Filter by ref, by first name and by name.

To address in this ticket if possible: #38

Document Cognito email pool creation

  • Only attribute is email
  • Create a Public Client app, with read-only capabilities (people that can successfully log through this app, typically from a web browser, can only read their information, not modify them)
  • Configure email/SMS contents

We cannot create more than 10 users at once

  • This is because we cannot send more than 10 UserUpserted events at once
  • In such a failure, database entries should be rolled back ==> creation should be @transactional!

Nb of users that can be created in batch is bounded by the number of events we can send at once. This is because send multiple batch of events and that some of them fail, we have now way of taking back all the other events that were successfully sent. As EventBridge.PutEvents can only handle 10 events at once, we must limit user creation to 10 users
https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_PutEvents.html

Prevent big page offset

Our current pagination is translated into offset-limit pagination by Postgres.
The more P=page*pageSize increase, the longer Postgres takes to process the request.
In particular, P could lead to a full scan.
To prevent this, P should be bounded.
Eg: P_MAX=1_000 ensures that a query will never scan more than P_MAX+MAX_PAGE_SIZE.
P_MAX=1_000 is large enough to cover all the use cases of the API.
* We don't expect consumers to dump the whole database
* Consumers are only expected to find users by weak comparison on
* ref
* firstname
* name

fee.status and fee.remaining_due should be transient

Do not persist fee.status and fee.remaining_due in db. Just compute them on the flight, in memory.

Do not create new flyway script migration. Just edit the current v0.3 then manually fix dev db accordingly.

When done, squash obtained commit with the fees commit in dev

IT seems to be polluting dev/prod environments

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.