You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lifecycle method componentDidCatch() for catching every error in the component or subcomponent rendering
In React <16 the UI stayed untouched when such an error happend
But in React >=16 the Component is getting unmounted from the UI completely when there is no componentDidCatch()
which results in a blank page
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
no verbs -> just nouns for Resources: /applications or /applications/123
Possible Responses: Collection of Resources (e.g. with Links) or One instance of a Resource
Keep your API course grained to be scaleble to future requirements
For Resources: Be as specific as possible: /customers vs. /newsletter-customers and /registered-customers
PUT for Create: Can be used when the Client has the ability to create an identifier for the Resource himself. But it has to contain a full replacement of the dataset: PUT /applications/123
Datenschutz - EU Datenschutz-Grundverordnung (EU-DSGVO)
Verschlüsselung
Die neue EU-DSGVO (EU-Datenschutz-Grundverordnung - tritt ein am 25.05.2018) fordert, dass Kundendaten verschlüsselt gespeichert werden. Und zwar so, dass nur der Urheber (also man als Unternehmen selbst und nicht der Cloud-Anbieter) Zugriff auf die Kundendaten hat. Man muss also die alleinige Gewalt über ihre Daten garantieren.
Data in Motion vs. Data at Rest
Encryption in Motion dient dazu, Daten während der Übertragung (z.B. Hochladen von Daten auf S3 oder Abfragen von Daten im RDS) zu verschlüsseln.
Werden Daten verschlüsselt gespeichert, sind diese Encrypted at Rest. Daten, die in S3, RDS oder einem anderen persistenten Datenspeicher gespeichert sind, sollten in der Regel verschlüsselt werden. Für Data at Rest Verschlüsselung gibt es zwei Möglichkeiten:
Clientseitige Verschlüsselung - Der Admin verschlüsselt die Daten vor dem Absenden, anstatt sie in AWS zu verschlüsseln. Er kümmert sich um den Versc