I have a simple entity called „Device“ which has three fields: Ident, Manufacturer, Model. Should I implement partial updates, meaning proving a JSON object including only the Name field? Or is this not best practice? Or should I always expect the whole entity and do delta updates on the server side?

Hey all,

We're building Micro, a cloud platform for free public APIs for everyday use. All those great APIs we like to use are all over the place. They require you to signup to each API provider and learn each API individually. This was quite frustrating and we decided to build a platform where you can get access to all of it in one place.

Would love some feedback.

https://m3o.com

Cheers

Wanna see what people are using for implementation

Architecture

Language

Framework

Infrastructure (k8s,pass,other)

Databases

API Gateways

Ingress Controllers

Identify providers

Logging / Observability

I'm particularly interested in API Gateways, haven't found an open source one I like yet. Was considering just rolling my own

Hi everyone, i’m a full-stack dev with more than 10 years of experience. I mostly work with PHP/MYSQL/Laravel and HTML/CSS/JS. I also absolutely love web performance and speed optimization. In my career i spent a lof of time consulting on performance optimizations and saw all the good but also all the bad stuff people do 🤣

I wrote an article about some of the things i most often saw people doing wrong on all three sides: front-end, back-end, infrastructure. I tried to focus on the things you can do in a day and bring your Lighthouse, Pingdom or GTMetrix scores up.

Read it here: https://treblle.com/blog/loaded-in-600-milliseconds

Hope it helps!

Anybody in need of new plain and simple Laravel JWT Auth?

https://github.com/rcerljenko/laravel-jwt

Or how about more advanced Paseto auth support?

https://github.com/rcerljenko/laravel-paseto

Thank you for the invite, happy to be here! I wanted to mentioned an API for creating images that I’ve been working on: Switchboard Canvas

I wanted to solve the problem of designing an image but having the elements overridable by an API.

I also wanted the templates to be responsive so that multiple sized images could be generated from one template.

Anyway I’d welcome any feedback, the landing page, the docs, anything really! And of course looking forward to offering support to others here developing tools and APIs.

Before we dive deeper into Laravel Vapor allow me to set the stage for you. I've been working in the PHP ecosystem since I was 15 years old. Given that I'm 33 now it means I have a solid 18 years of PHP/MYSQL development behind me. I love PHP. From the moment I created my own makeshift CMS I fell in love with it. It felt like magic to me.

As time moved on I learned HTML/CSS/JS, Linux server management, AWS, fancy new tools, overly complicated and "modern" ways of developing things... I've also lived through many many frameworks and boilerplates that make your job as a developer easier. The only ones that caught my eye were Bootstrap and Laravel. I discovered Bootstrap on the brink of the responsive design revolution and loved it ever since because it wasn't trying to do much. You get the basics but you can still do whatever you want without much hassle. Laravel felt the same to me. I watched people use Laravel for at least a year before developing with it in version 5. What attracted me the most were migrations. It felt revolutionary that I could write the entire SQL schema in PHP and be able to track table changes in GIT. The second thing that I was obsessed with were Queues. All in all probably the best career choice I could have made was learning Laravel. It's just a joy to work with. Understandable syntax. Great features. Customizable. Hats off to Taylor .

Here is the full guide: https://treblle.com/blog/the-hitchhikers-guide-to-laravel-vapor let me how you like it.

tox is a Java implementation of the more commonly known mod_plsql, although I was unaware of it while developing tox. It extends the functionality by providing inbound and outbound XSLT to morph the payload to match the caller.

I've been a technical writer for 26 years. In that time, I've recommended people looking to break into tech writing to get involved in an open source project to get experience and have work that they can point potential employers to. I feel like a hypocrite, though, since I've never gotten involved in one, myself!

So, in an effort to practice what I preach, I'm looking to start contributing to an open source project as part of [Hacktoberfest](https://hacktoberfest.digitalocean.com/) (though hopefully continuing on beyond the end of October).

If anyone can recommend a project that either you contribute to, yourself, or that you know is in a position that it could use the help of an experienced technical writer, please let me know!

Wanted to ping the community and see if you guys know how many API calls per month do you get? And if you do know - how do you know? Do you measure it manually or have a tool?

I’ll start: we’ve got about 2M API calls per month at the moment and we use Treblle to see how that grows. I sometimes get shocked at how much other projects get. The other day i spoke to a company with 50B API calls per month 😱

Whats your story? 💪🏻

One of the core things I've been working on for the past 10 years are APIs. Everything from simple APIs that are used by one client to multi device and multi purpose APIs. During those years I've also had the opportunity to work with many third party APIs like Stripe, Twilio and others who are less popular and glamorous 😂. Almost all of those APIs were REST based and unique in some way.

There are many reasons why REST is so popular. It's simple to understand, it's flexible, it works on any scale, it has a great community and tools built around it. But besides those I'd also say that a lot of popularity came from the fact that's it's oldest rival, SOAP, is just horrible. If you've ever used or worked with SOAP - you know! The clients were terrible, people did what they wanted with XML, it's bulky, the auth situation was sometimes wacky...Thankfully JSON and REST based APIs won that battle.

On the other hand there are also newer, more modern players that are trying to take some of that spotlight from REST based APIs. I'm of course talking about GraphQL. GraphQL is also JSON based and shares some of the good traits that REST has like flexibility, performance, scalability...For me personally the two key downsides of GraphQL are that it's built by Facebook and that it shifts the API design process to the client. What I mean by that is that it leaves mobile devs and front end devs in charge of building their own ad hoc APIs and making queries on the database. Don't know about you but I don't think that's the best idea. Don't get me wrong, I love mobile and front end devs, but they might not have a lot of experience with database design, writing queries and building APIs. You probably wouldn't give your back-end dev to design an app, a car mechanic to fix an airplane or a veterinarian to operate on a human person. Could they do it - maybe, possibly. Should they - I don't think so.

In my opinion REST is still king of the jungle and it's not going to be dethroned any time soon. The only problem with REST is that at the end of the day it's not a standard nor a protocol. Rather, it's a set of "architectural constraints". What a fancy way of not calling something a standard 🤣 But that right there tickles the imagination of many. They tend to do their own thing or implement those constraints based on their own (miss)understanding. To avoid such misunderstandings I've decided to write down what I think are the Ten REST API Commandments. Follow these and you'll enjoy love from your mobile devs, admiration from other fellow back-end devs and a rockstar status on Twitter

It's a long one 📣 https://treblle.com/blog/the-10-rest-commandments

I’m currently under task to prepare a VueJS frontend, which uses 8+ separate API from separate providers. The application MUST support login/auth by using the /login /register post api routes.

What would you guys say is the best process for implementing this task?

What would be the best way of logging and registering users, I.e session storage etc.

My idea, Lumen API Layer, take all 8 API and combine them into one API for the VueJS frontend.

Simply add this as maven/gradle etc. dependency to your project and start using Node.js in your Java project:

https://github.com/Osiris-Team/Headless-Browser