The document discusses performance challenges in API projects, particularly focusing on speed and efficiency in data handling and execution of queries. It emphasizes the importance of reducing query counts and data loading methods to enhance performance, along with techniques for overcoming bottlenecks like eager loading and serialisation issues. The suggestion includes exploring property filtration and considering the algorithmic complexity of queries to optimize performance.

1. Need for Speed
Removing speed bumps in API Projects
Łukasz Chruściel
https://sm.ign.com/ign_in/screenshot/default/nfs-most-wanted_qxww.jpg

2. Introduction

3. Weavers, Sylius

4. Why do we need to thinks
about performance?

5. ~ Amazon
“100ms Faster
=
1% More Revenue.”

7. The most common performance bottlenecks
0
15
30
45
60
Amount of queries to DB Cost of object serialization Latency Framework
5
4
28
56
Votes

8. Algorithmic complexity

10. Project structure

12. Problems 🎉

13. N+1

14. ORM anyone? 🧐

15. Product list

16. Let’s start small
{
"@context":"/api/contexts/Product",
"@id":"/api/products",
"@type":"hydra:Collection",
"hydra:totalItems":6,
"hydra:member":[
{
"@id":"/api/products/1",
"@type":"Product",
"id":1,
"name":"T-Shirt",
"price":1000
},
{
"@id":"/api/products/2",
"@type":"Product",
"id":2,
"name":"Trousers",
"price":5000
},
{
"“…“":"“…“"
}
]
}
Amount of products: 6
No associations between objects
Sample query on the left

18. O(1)

20. Order list

21. How many queries are executed here?
{
"@context": "/api/contexts/Order",
"@id": "/api/orders",
"@type": "hydra:Collection",
"hydra:totalItems": 3,
"hydra:member": [
{
"@id": "/api/orders/1",
"@type": "Order",
"id": 1,
"orderItems": [
"/api/order_items/1",
"/api/order_items/2"
]
},
{
“…”: “…“
}
]
}
Amount of orders: 3
Every order associated with 2 items
Sample query on the left
No total
fi
eld

24. O(N)

26. Order list with additional
fi
eld

27. How many queries are executed here?
{
"@context": "/api/contexts/Order",
"@id": "/api/orders",
"@type": "hydra:Collection",
"hydra:totalItems": 3,
"hydra:member": [
{
"@id": "/api/orders/1",
"@type": "Order",
"id": 1,
"orderItems": [
"/api/order_items/1",
"/api/order_items/2"
],
"total": 7000
},
{
“…”: “…“
}
]
}
Amount of orders: 3
Every order associated with 2 items
Sample query on the left
Added “total()” as a function of product
price and quantity of item

29. O(N*M) or O(N^2) 🚀

33. How to spot it?

35. How to
fi
x it?

36. Upfront data loading

37. #[ORMOneToMany(fetch: ‘EAGER')]
Eager loading

38. final class LoadItemsAndProductsExtension implements QueryCollectionExtensionInterface,
QueryItemExtensionInterface
{
private function apply(QueryBuilder $queryBuilder): void
{
$queryBuilder
->addSelect('oi', 'p')
->join(OrderItem::class, 'oi', Join::WITH, 'oi.originOrder = o')
->join(Product::class, 'p', Join::WITH, 'oi.product = p')
;
}
}
Custom query

39. So is single query an ultimate
solution?

40. ⚠ Not so fast ⚠

41. Joins are expensive 💰

42. Serialisation

43. Problem vectors
Size of data
Process of
serialisation

44. Process of
serialisation

45. Serialisation process
oversimpli
fi
ed

46. [
'id' => 1,
'name' => 'T-Shirt',
'price' => '1000'
]
Application
Database

47. [
'id' => 1,
'name' => 'T-Shirt',
'price' => '1000'
]
Hydration 🧙
new Product()
Application
Database

48. [
'id' => 1,
'name' => 'T-Shirt',
'price' => '1000'
]
Hydration 🧙
new Product()
Application
Serialization ⚙
{
‘id': 1,
‘name': 'T-Shirt',
‘price': '1000'
}
Database Frontend app

49. [
'id' => 1,
'name' => 'T-Shirt',
'price' => '1000'
]
Hydration 🧙
new Product()
Application
Serialization ⚙
{
‘id': 1,
‘name': 'T-Shirt',
‘price': '1000'
}
Database Frontend app
🤡

50. Full stack vs API

51. Solution - Pre-computing

54. Sylius order

56. Saving serialised objects

57. View models doesn’t have to
be models 🤯

58. 1. Store read models in key-value storage
2. Restore it by indexed key

59. Size of data

60. Entity lifecycle
oversimpli
fi
ed

61. Order
{
"items": [
{
"productName": "Mug",
"quantity": 3,
}
]
}
1. Cart

62. {
"items": [
{
"variant": "/api/v2/admin/product-variants/MUG
"productName": "Mug",
"id": @integer@,
"quantity": 3,
"unitPrice": 2000,
"originalUnitPrice": 2000,
"total": 6000,
"units": [
"/api/v2/admin/order-item-units/@integer@"
"/api/v2/admin/order-item-units/@integer@"
"/api/v2/admin/order-item-units/@integer@"
],
"fullDiscountedUnitPrice": 2000,
"subtotal": 6000
}
]
}
Order
1. Cart
2. Product details

63. {
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
"city": "New York",
"postcode": "90000"
},
"billingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
"city": "New York",
"postcode": "90000"
},
"items": [
{
"productName": "Mug",
1. Cart
2. Product details
3. Address
Order

64. Order
{
"payments": [
{
"@id": "/api/v2/admin/payments/@integer@",
"@type": "Payment",
"id": @integer@,
"method": "/api/v2/admin/payment-methods/CASH_
}
],
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
"city": "New York",
"postcode": "90000"
},
"billingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
1. Cart
2. Product details
3. Address
4. Payments

65. {
"shipments": [
{
"@id": "/api/v2/admin/shipments/@integer@",
"@type": "Shipment",
"id": @integer@,
"method": "/api/v2/admin/shipping-methods/UPS"
}
],
"payments": [
{
"@id": "/api/v2/admin/payments/@integer@",
"@type": "Payment",
"id": @integer@,
"method": "/api/v2/admin/payment-methods/CASH_
}
],
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
Order
1. Cart
2. Product details
3. Address
4. Payments
5. Shipments

66. {
"shipments": [
{
"@id": "/api/v2/admin/shipments/@integer@",
"@type": "Shipment",
"id": @integer@,
"method": "/api/v2/admin/shipping-methods/UPS"
}
],
"payments": [
{
"@id": "/api/v2/admin/payments/@integer@",
"@type": "Payment",
"id": @integer@,
"method": "/api/v2/admin/payment-methods/CASH_
}
],
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
Order
1. Cart
2. Product details
3. Address
4. Payments
5. Shipments
6. Available shippings
7. Available payments
8. Product categories
9. Images
10.…
1. Cart
2. Product details
3. Address
4. Payments
5. Shipments

67. {
"shipments": [
{
"@id": "/api/v2/admin/shipments/@integer@",
"@type": "Shipment",
"id": @integer@,
"method": "/api/v2/admin/shipping-methods/UPS"
}
],
"payments": [
{
"@id": "/api/v2/admin/payments/@integer@",
"@type": "Payment",
"id": @integer@,
"method": "/api/v2/admin/payment-methods/CASH_
}
],
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
1. Cart
2. Product details
3. Address
4. Payments
5. Shipments
6. Available shippings
7. Available payments
8. Product categories
9. Images
10.…
Performance📉
Order

68. {
"shipments": [
{
"@id": "/api/v2/admin/shipments/@integer@",
"@type": "Shipment",
"id": @integer@,
"method": "/api/v2/admin/shipping-methods/UPS"
}
],
"payments": [
{
"@id": "/api/v2/admin/payments/@integer@",
"@type": "Payment",
"id": @integer@,
"method": "/api/v2/admin/payment-methods/CASH_
}
],
"shippingAddress": {
"@id": "/api/v2/admin/addresses/@integer@",
"@type": "Address",
"firstName": "John",
"lastName": "Doe",
"countryCode": "US",
"street": "Avenue",
1. Cart
2. Product details
3. Address
4. Payments
5. Shipments
6. Available shippings
7. Available payments
8. Product categories
9. Images
10.…
Order

69. Size do matter

70. –ANGRY DEVELOPER
“BUT I NEED ALL THAT DATA 🤬”

71. Do you? 🧐

72. Solution - split data

73. {
"orderItems": [
{
"product": "/api/products/1",
"quantity": 4
},
{
"product": "/api/products/2",
"quantity": 1
}
],
"total": 9000
}
{
"orderItems": [
{
"product": {
"name": "test2",
"price": 1000
},
"quantity": 4
},
{
"product": {
"name": "Trousers",
"price": 5000
},
"quantity": 1
}
],
"total": 9000
}
Atomic objects (Edge Side API)

74. Do you need it all the time? 🧐

75. Solution - more variations

76. Property
fi
ltration

77. ?properties[]=<property>&properties[<relation>][]=<property>

78. Property
fi
ltration
GraphQl

79. Property
fi
ltration
GraphQl
Vary header

80. –mdm web docs
“The Vary HTTP response header describes the parts of the request
message aside from the method and URL that in
fl
uenced the content
of the response it occurs in. Most often, this is used to create a
cache key when content negotiation is in use.”

81. Summary

82. Measure, measure, measure…

83. Top Gun: Maverick

84. Remember about algorithmic complexity of your queries
Do not hydrate too much data
Think out-of-the box of your “entities”

86. Thank you!