Crausaz Samuel (@letamtam) header
Crausaz Samuel (@letamtam) profile picture
Fribourg
Joined December 2006
Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)Photo by Crausaz Samuel (@letamtam)
1
124
1
764
143,372
SWOT Analysis
1
237
2
1,041
183,545
Making Decisions
19
98
21,493
Crausaz Samuel retweeted
Canva : 5 nouveautés majeures à découvrir blogdumoderateur.com/canva-5…
1
50
Crausaz Samuel retweeted
How Jakob Nielsen Developed the 10 Usability Heuristics jakobnielsenphd.substack.com…
1
1
420
Crausaz Samuel retweeted
Explaining 9 types of API testing. 🔹 Smoke Testing This is done after API development is complete. Simply validate if the APIs are working and nothing breaks. 🔹 Functional Testing This creates a test plan based on the functional requirements and compares the results with the expected results. 🔹 Integration Testing This test combines several API calls to perform end-to-end tests. The intra-service communications and data transmissions are tested. 🔹 Regression Testing This test ensures that bug fixes or new features shouldn’t break the existing behaviors of APIs. 🔹 Load Testing This tests applications’ performance by simulating different loads. Then we can calculate the capacity of the application. 🔹 Stress Testing We deliberately create high loads to the APIs and test if the APIs are able to function normally. 🔹 Security Testing This tests the APIs against all possible external threats. 🔹 UI Testing This tests the UI interactions with the APIs to make sure the data can be displayed properly. 🔹 Fuzz Testing This injects invalid or unexpected input data into the API and tries to crash the API. In this way, it identifies the API vulnerabilities. -- Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐜𝐡𝐞𝐚𝐭 𝐬𝐡𝐞𝐞𝐭. After signing up, find the download link on the success page: bytebytego.ck.page/da4d43d0e…
16
490
7
1,889
112,284
12 Tips For API Security > Use HTTPS > Use OAuth2 > Use WebAuthn > Use Leveled API Keys > Authorization > Rate Limiting > API Versioning > Allow list > Check OWASP API Security Risk > Use API Gateway > Error Handling > Input Validation
272
2
863
44,381
SSO
24
85
4,783
Single Sign On (SSO)
81
362
24,369
Crausaz Samuel retweeted
CAP, BASE, SOLID, KISS, What do these acronyms mean? The diagram below explains the common acronyms in system designs. 🔹 CAP CAP theorem states that any distributed data store can only provide two of the following three guarantees: 1. Consistency - Every read receives the most recent write or an error. 2. Availability - Every request receives a response. 3. Partition tolerance - The system continues to operate in network faults. However, this theorem was criticized for being too narrow for distributed systems, and we shouldn’t use it to categorize the databases. Network faults are guaranteed to happen in distributed systems, and we must deal with this in any distributed systems. You can read more on this in “Please stop calling databases CP or AP” by Martin Kleppmann. 🔹 BASE The ACID (Atomicity-Consistency-Isolation-Durability) model used in relational databases is too strict for NoSQL databases. The BASE principle offers more flexibility, choosing availability over consistency. It states that the states will eventually be consistent. 🔹 SOLID SOLID principle is quite famous in OOP. There are 5 components to it. 1. SRP (Single Responsibility Principle) Each unit of code should have one responsibility. 2. OCP (Open Close Principle) Units of code should be open for extension but closed for modification. 3. LSP (Liskov Substitution Principle) A subclass should be able to be substituted by its base class. 4. ISP (Interface Segregation Principle) Expose multiple interfaces with specific responsibilities. 5. DIP (Dependency Inversion Principle) Use abstractions to decouple dependencies in the system. 🔹 KISS "Keep it simple, stupid!" is a design principle first noted by the U.S. Navy in 1960. It states that most systems work best if they are kept simple. Over to you: Have you invented any acronyms in your career? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/3KCnWXq
9
487
5
1,865
183,102
Crausaz Samuel retweeted
16 Must-Know System Design Concepts 1. Domain Name System (DNS) 2. Load Balancer 3. API Gateway 4. CDN 5. Forward Proxy vs. Reverse Proxy 6. Caching 7. Data Partitioning 8. Database Replication 9. Distributed Messaging Systems 10. Microservices 11. NoSQL Databases 12. Database Index 13. Distributed File Systems 14. Notification System 15. Full-text Search 16. Distributed Coordination Services levelup.gitconnected.com/16-…
13
734
9
2,920
346,961
Crausaz Samuel retweeted
The Psychology Behind Highly Effective Landing Pages growth.design/case-studies/l…
2
4
929
Never gets old😂 (Software Engineering 101)
62
483
108
1,719
202,745
5 Principles of Object Oriented Design (SOLID) 🚨 Join Waiting List for New 10+ Hour Linux Course - bit.ly/44CI2bK #java #javaarrayclass #javaclass #javascript #Objectorienteddesign #SolidJava #SoftwareEngineering
2
120
1
441
39,631
What are the main components of Docker? Building and deploying applications has its complexities. Software inconsistencies across different environments lead to significant issues including deployment failures, increased development and testing complexity, and more. Docker solves the "it worked on my machine" problem, and streamlines application deployment by encapsulating applications and their dependencies into standardized, scalable, and isolated containers (containerization). Docker has a handful of core components powering the technology. By understanding them you will have a strong fundamental understanding — Let's dive in! Images: Read-only templates that are used to build containers. Images are created with Dockerfile instructions or can be downloaded from a Docker registry like Docker Hub. Container: An instance of an image. It's a lightweight, standalone package that includes everything needed to run an application. Dockerfile: A script-like file that defines the steps to create a Docker image. Docker engine: The Docker engine is responsible for running and managing containers. It's composed of the Docker daemon and the Docker CLI that communicates through REST API. Docker daemon: The daemon is a persistent background service responsible for managing objects. It does so via listening for API requests. Docker objects include images, containers, networks, and storage volumes. Docker registry: Are repositories where Docker images are stored and can be distributed from. Docker registries can be public or private. Docker Hub is the default public registry that Docker is configured with. Docker network: Containers run on networks allowing them to communicate with each other and the outside world. The network provides the communication gateway between containers running on the same or different hosts. Volumes: Allow data to persist outside of a container and to be shared between container instances, even after a container is deleted. Volumes decouple data life from the container lifecycle. The components listed above all tie together to produce a simple system for developers to automate the deployment, scaling, and management of applications. This has led Docker to become a powerful and integral tool in modern software development.
23
166
585
88,326
Crausaz Samuel retweeted
Top 7 Ways to 10x Your API Performance 1. Pagination This is a common optimization when the size of the result is large. The results are streaming back to the client to improve the service responsiveness. 2. Asynchronous Logging Synchronous logging deals with the disk for every call and can slow down the system. Asynchronous logging sends logs to a lock-free buffer first and immediately returns. The logs will be flushed to the disk periodically. This significantly reduces the I/O overhead. 3. Caching We can cache frequently accessed data into a cache. The client can query the cache first instead of visiting the database directly. If there is a cache miss, the client can query from the database. Caches like Redis store data in memory, so the data access is much faster than the database. 4. Payload Compression The requests and responses can be compressed using gzip etc so that the transmitted data size is much smaller. This speeds up the upload and download. 5. Connection Pool When accessing resources, we often need to load data from the database. Opening the closing db connections add significant overhead. So we should connect to the db via a pool of open connections. The connection pool is responsible for managing the connection lifecycle. On 6 and 7, we created a video about this topic and included 2 more ways to improve performance. Watch and subscribe here: lnkd.in/e5JJfbcs
24
568
5
2,156
244,925
How to be insanely productive. The 5 rules of peak productivity (better than the Pomodoro technique):
38
179
10
1,118
359,919