launch day🔥 released my new book System Design with Laravel - 267 pages of high-quality content - system design from scratch - designing real-world systems - planning different projects - databases, caching - ...and more grab your copy now

still the best code analysis tool out there

Teslas have the lowest maintenance & repair costs of any brand

by the way we're building Horizontal. the best search platform for your team that will give you pure joy not PTSD https://t.co/iwYYu8BFy6

if tech products were honest slack

If you have any Laravel or development-related questions, just drop a DM! I'd be happy to help if I can.

There's an official Laravel package called pail. It's a log-tailing package that provides real-time log monitoring directly from Artisan. Very nice👌

14/14 Thank you if you're still here! If you're experiencing challenges while designing new systems or complicated features, my team and I can help you. Just drop a DM and let's talk!

13/14 That’s it! We have our "mini application" inside our app that handles a specific 3rd party. Nice and easy.

12/14 These requests can be used pretty easily:

11/14 In the parent GumroadService we can configure the access token:

10/14 To make our lives even easier, we can use a package to handle requests. Saloon is a great one, but in this example, I'm using laravel-transporter. With this package, the GetProductRequest looks like this:

9/14 But now we have to use every request separately. Which is fine, but not so convenient, so we can use these requests in the GumroadService:

8/14 Each request class implements one API endpoint:

7/14 If you think about it, these methods, such as the `product()`, are requests. Why don’t we treat them as if they were form requests? Let’s put ‘em in separate classes:

6/14 With this approach, we have one class for the whole API, and each endpoint has a method. This is perfectly fine and works 99% of the time. However, there are some situations when the API is simply too big to put everything in one class.

5/14 Now everything is ready to actually implement the GumroadService class:

4/14 Each service can have its own service provider. This is the perfect opportunity to use Laravel’s singleton bindings. We can create a new instance using the configuration values:

3/14 In Laravel, we have the services.php config file. This is the perfect place to configure our 3rd parties:

2/14 In the Services folder, I create a new folder for each 3rd party and treat it like it were a mini-application inside my app. It looks like this:

1/14 Treat your 3rd parties as if they were mini-applications inside your application. They have their own namespaces, DTOs, service classes, and so on. Something like this:

💡 How to integrate 3rd parties into your application? We must integrate with many 3rd party APIs and SDKs in every project. You can treat them as mini-applications inside your app. 🧵Keep Reading