Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "rest"
-
Sister: "You can't commit to......"
Me: *has flashbacks of Git Commit issues doesn't even hear the rest*6 -
The CEO at the company I work at has been telling our partners that our PIA is ready. It took me a week to figure out what the hell a PIA was but he actually meant API6
-
Funny. Drunk, standing here waiting for my fries and thinking about rest api implementations. I'm weird.4
-
REST clients today can use upwards to 1000MB of memory. This leads to a poor experience for people who don't have access to high power machines, such as those in developing countries. So I built a REST client that uses ~60MB.
Introducing Nightingale, a fast and resource efficient REST client for Windows 10.
Let me know what you think! Looking forward to your feedback 🙏🏽
https://microsoft.com/store/...rant rest api xaml dotnet uwp windows 10 windows nightingale rest client postman csharp postman rest api29 -
That moment when you finished your first REST API 🎉
And you realise all it can do is useless ☹️
But then you realise, you can extend the functions easily with you new knowledge 🎊
Man, this emotional up an down is exhausting 😆4 -
Rest In Peace My Dad. now he is going to follow my uncle. the best two person and developers in my world. as a lone survivor, your memory will continue to be remembered propagate through my life.
for fellow devRanters, Always love your family more when they're still in your side. doesn't matter how harsh, how bad they are; you can always find the meaning, the values life will give you, and that will be the best presents your parent will give you. Always. stay creative, they will be proud.
the short story of my dad : https://devrant.com/rants/1630147/...37 -
"What technologies do you know?"
"I can write pretty URLs that return JSON"
"You mean REST?"
"No, I mean pretty URLs that return JSON"3 -
Client: "Hey we want you to integrate your product with our system."
Me: "Oh, OK. Where's your API?"
Client: "Here! We even have an outdated .Net SDK, we use XML."
Me: "Ok.. how do we authenticate? What's your OAuth 2.0 endpoint?"
Client: "O auth what?"
Me: " You know, the current standard for REST API authentication and authorisation"
Client: " What's REST?"
*Hungs up*8 -
Why in God's name would anyone use SOAP over Rest......
Because it makes you cleaner hahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahaha9 -
That moment you leave the office for the last time in 2018.
FAWK YEAH!
What a year it’s been, from learning new platforms, to developing never ending changes, to breaking production at Christmas time, and finishing the year at the peak of purchasing period on a couple of websites with no reason to care what happens for several weeks all while absorbing extra projects from resigning co-workers.
*Turns on autopilot and walks the fuck out*
From one exhausted dev to the rest of you, enjoy the holiday break!3 -
Why on Earth would an API require me to provide input like this?
{"this": "{\"is\": \"not\"}", "how": "{\"json\": \"works\"}"}
😡7 -
Hey, thanks for teaching me JavaScript and HTML. I almost feel like a web developer now.
What about the REST?4 -
Currently working on the privacy site CMS REST API.
For the curious ones, building a custom thingy on top of the Slim framework.
As for the ones wondering about security, I'm thinking out a content filtering (as in, security/database compatibility) right now.
Once data enters the API, it will first go through the filtering system which will check filter based on data type, string length and so on and so on.
If that all checks out, it will be send into the data handling library which basically performs all database interactions.
If everything goes like I want it to go (very highly unlikely), I'll have some of the api actions done by tonight.
But I've got the whole weekend reserved for the privacy site!20 -
I feel sad for some of my officemates. They are required to go to office today due to client support stuff, and it's a Sunday. They should be resting, be with their family/love ones/pet/bed, playing games, or whatever they want to do on a rest day. :(8
-
"LeT's uSe gRaPhQL!" They said.
"It EliMinAtEs cOmpLeX aNd vErBoSe REST coDe!" they said.
Me sitting here for hours waiting for the backend team to fix major regressions every time they push the smallest "updates" to staging... 🤡
Call me a boomer but I can't help but feeling graphQL makes things MORE complex than REST... either that or the backend devs have no idea what they are doing17 -
Is it me or all REST api use json today ?
And xml is kinda dead ?
I always feel awful when I see an xml rest api.10 -
Fucking IT and their self signed corporate proxy SSL bullshit getting in the way of anything that needs to verify SSL requests,
Fuck you for making my day a slow and miserable day and having to resort to forcing rest apis and SDKs to work over HTTP instead, all in the name of “Security”.2 -
I don’t work without rest. In fact, I rest during the work. I was once got caught by the director(3 level above me) while sleeping in my cubicle.5
-
[Begin Rant] When you show your senior manager your REST Web Service and he says "Oh no nooo... I don't wanna see no code"... Me: Code?? That ain't code you fat silly fucker it's the command line output data which I spent a week parsing, batch processing, and storing into the database! [End Rant] :[4
-
Would you rather only be able to use Internet Explorer for the rest of your life or only use Light themes also for the rest of your life?15
-
Sometimes the best thing to do is to rest during a weekend and do an activity away from software.10
-
Me: please return http code 202 in your http service.
My collegue: ok.
After one hour...
Me: you are returning 200, I told you 202. Let me see the code:
OMFG she was writing the string "202" in the response body!!!
I do not know how to escape from all of this shit.1 -
Ok, so our team is responsible for writing an app that consumes an API written by the client's team (I refuse to call it a "REST" API, despite their claims). On one of the clarification meetings we are discussing an endpoint that accepts a (logically) unique field multiple times, even though an entity is already registered in the system with that unique identifier. Our proposal would be that this API of theirs should not happily accept duplicates as many times as there are bits on a 4TB hard drive, rather it should signal an error.
The response we got is this: Due to the Separation of Concerns principle they thought that it should be our app's responsibility to not send a request if an entity with said field is already in the system. Thus there's no need for the backend to validate this.
I didn't hear the next part, because I had to collect my headphones from the other side of the room where they were flung in rage.11 -
I have discovered a fresh hell
Some guy I’ve never met or heard of in the office lobbed a comment at one of my *approved and merged* pull requests. He doesn’t say anything specific, only that my REST urls are not in line with naming convention. That’s all he says, and I’ve already walked the URL consumers through the code and given them the URLS.
I’m really annoyed that this guy won’t just say what he has in mind, but fine whatever this is a professional environment and developers are not known for being a diplomatic people. Let it go and get your work done!
I do some googling and find an obvious change that needs to happen- I implement it, open a new pull request and inform my URL consumers of the change.
This rando still isn’t satisfied and still won’t say what needs to change. I am on round 3 of this wonderful cycle and this guy is acting all fuckin HAUGHTY about it. “Here is a list of conventions I found googling, you should read them even if it takes 4 hours because it will benefit your career”
Sure dog you’re probably right on that one but we are in a professional environment and at this point you are holding up production so you can wave your dick around! Just SAY WHAT YOU MEAN SO WE CAN MAKE THE CHANGES AND GET OUR WORK DONE4 -
Neo: "Why do my eyes hurt?"
Morpheus: "You've never used them before... REST Neo, the answers are coming"
See; it was never SOAP!3 -
I really can't focus on anything else when there's an unfinished assignment or a deadline approaching.. I debug in my sleep and daydream in public transport thinking about all the things I'll have to code later.
I hate it because I'm ignoring all my loved ones during days like these and it always backfires on me somehow. However, I can't help myself - I am always stressing out..3 -
Unemployment week 2
I finalized buying ~1000 square feet ( ~95 square meters ) apartment. Still renting 100 square feet room ( ~10 m2 ) so change will be tremendous. It’s first property I will own. With that amount of free space I think I can start constructing small spaceship or time travel machine.
Typed on linkedin that I’m offline.
Phone is still ringing. Time to turn it off for a while and rethink my life and world around from scratch.
Rest is good for my soul.
Peace ✌🏽2 -
Currently working on my first real REST api and I've arrived at the authentication part.
I'm not sure how to do this one, the client will have to login using username/password but then, what's the most conventional way of authentication logged in users through a REST api? (no oauth (yet))
This should be usable for anything like ajax requests to calls from the backend to curl requests.
Looking forward to ideas!30 -
!Rant
TLDR: What's your favorite REST API Documentation tool?
I'm about to start developing a really large REST API. I have never really had need to document my previous API's since they were small, self explanatory and had only me using them. Aside from this one being too large for me to keep track of there is also a remote team that will need to integrate with it.
Basically I need write exceptional documentation while using as little time as possible. I love postman and am planning to use it for documentation since I currently use it to test during development anyway but I have seen some really neat looking tools like swagger and apiary so I figured I would check for some other suggestions.
What is your current / preferred REST API documentation method?13 -
Made my first Node.js Todo list today! Got myself a new front end design tool, Bootstrap Studio (50% off). Learned about REST, using Node as an API and MongoDB and Angular! Had a lot of fun learning and I would recommend it to anyone that's a Node.js beginner. I want to do a video tutorial series on Node.js, is that a good idea?9
-
Please stop calling calling rest to any json over http api. That's not rest, rest has its specifics details to be called rest.11
-
That joy feeling when you are finally rewriting the backend and frontend with GraphQL instead using the fuckin old undocumented REST API who was written by fuckin amateur ex-coworker.7
-
Just spent over 5 hours trying to figure out Microsoft’s OneDrive REST api. Basically my first time trying to do POSTs n’ stuff. I got very very close, but the server kept throwing 400 error codes. Eventually I had to give up and ask Stack Overflow. Going to bed now at 2:20am. No worse feeling then not being able to solve a problem you’re dedicated on solving. :/4
-
Dear API vendor,
Please get off your arse and learn about REST, OpenAPI, JSON Schema, XSD and basic documentation so that I don't have to guess how to use your shitty, inconsistent, RPC over HTTP service.
With Love,
Platypus2 -
GraphQL people: REST sucks because it causes unnecessary data fetching and extra requests.
Also GraphQL people: "PicoLooper - A <200 LOC 🤏 ninja-grade 🥷 bulletproof 🔫 solution for the n+1 request problem 🙅 made with love ❤️" -
Since a few days I have my first dev job in a small it company. At my first day I directly stared to implement a rest api for managing dns servers.
Today I completed the prototype and all works well. What a feeling :)5 -
Anyone here has an idea of a project to do in Java and Spring (REST stuff) ?
I'm out of ideas :/ and I really want something to build in Java and keep me busy for a while.7 -
This is the story of the API documentation.
Which btw I couldn't find on the producent's website anywhere. I had the pdf shared with me by a coworker.
I knew the api was fucked up the moment I looked at endpoint documentation.
GET params? WHERE, ORDERBY etc. Literally make a SQL select in a GET request.
Returned stuff? The whole thing. Not some DTO, you literally get everything you can get.
Eg if you get IP in your response, you get it in several formats: dotted form, as hex, and as int. In 3 different json fields.
Oh, and regarding IP - one would imagine you can use masks or prefixes for subnets, right? Nope. The only param you can use there is the subnet size. So you have to calculate the power of 2 every time you want to make a request.
That's from the endpoint documentation. But what about some general info on the API, before all that?
As I was looking for something, I decided to read that intro and general info about the API.
Okay, so there was a change log between API versions. "removed [endpoint which sounds like correct REST design], please use [this generic thing with SQL-like GETs]"... Several of them.
And there was also this sentence which said that the API is not restful, "it's REST-like". <facepalm>
If it was a bad attempt at REST API, I would let it go. But this sentence clearly showed they knew they did everything wrong. And the changelog showed they didn't stop there, they were actively making it worse.1 -
So, first: I'm a bit of a perfectionist when it comes to code and love to think I know everything.
We had a group project at university and me being laid back but unknown to the other people, the "rest" of them was together with me in a group. We got to know each other and actually we were a pretty cool group. I guess "the rest" in a computer science course means you get the cool guys.^^
1/6 of us did ever code in C# and 2/6 even knows what an engine is and how unity works. I was in both sixths, got group leader somehow (if you'd know me from school. Omg. I was that one guy not knowing what went on, saying my two sentences at the presentation and took the B-.:D), so what to do to have a nice 2 weeks with them?
We did a crash course, I taught them some basics and everything.
The point is, i was hella nervous and i really get anxious if something is expected from me.
Long story short, I talked a whole week for 5-7 hours straight without real pauses and eating wayyy less a man should. Dude I was literally dead on my way home on friday evening. I felt like I would fall over any fucken second, i was all shakey, dizzy as hell, weird vision, everything. It felt like I was about to die on the spot.
I got home though, ate like 1/2 kilograms of pasta and felt myself coming back to life.:D
What to learn from this:
Keep the fuck calm, do pauses, drink and eat enough and don't rush all in for a fucken week without real rest..^^
It fucks you up and doesn't do anything good for your productivity.
We got an A btw, so in the end, all went good.(: -
My eyes hurt everytime our backend guy gives me a new REST API to implement in our app and always the formatting of the json is something like this. Like why can't you just fucking format it properly so I won't have to look at my code and feel disappointed for writing such ugly code. All because your lazy ass didn't care to understand the fundamentals of how json objects and arrays work !!! It's been a month since I've joined this company and I'm tired of explaining why we should use the status code for failure checking and not this stupid pass/fail status flag. I don't even remember how many times I've brought it up but everytime I get reasons like "Dude, you know what our server is never going to go down or fail so it doesn't even matter". And at that point I feel like I shouldn't even argue with him anymore.3
-
So lately I am learning about APIs and REST/ful architecture (I'm a plain beginner). I must say it's very interesting.
I find this website very very helpful as a practical implementation of the theory I've been consuming. I'd truly appreciate any recommendation on the subject.
https://apigee.com/console/twitter5 -
!rant
I made a project while learning spring!
Name - Restify
What is it? - Makes any program/script a rest service.
Link - https://github.com/gauravat16/...
Its really small now, I will keep learning and expanding it. 🙂2 -
I'm so pissed off at twitter REST API. On their site is a example: https://api.twitter.com/1.1/... but it doesn't work, Volley always returned 404, and guess what I tried. I changed the order of screen name and count to this: https://api.twitter.com/1.1/... and it works. I don't even. I sat there pulling my hair out for 2 hours just for this, fuck.3
-
I am so 😢🤒😡 right now. I applied for a remote job, so they gave me an assessment and the language was c++. The funny thing is that c++ was not in my resume.
So I decided to explore c++. "I don't know what the fuss is, C++ is not so hard". It was very easy for me to grasp. It took me two days to understand it.
Then I did one of those online test and I scored 58/60.
Now I went back to take the assessment test on C++ but lo and behold the assessment is now on Rest API.
But Rest API is also not on my resume. They are not assessing me on my strengths like Java or kotlin or python or my my lesser strengths like C# or JavaScript.9 -
I just learned the concept of this thing called REST API and now here's GraphQL showing up on me face. Mother fucking web development hell. BRB. KMS4
-
I need to encrypt some large files at rest and then decrypt them immediately prior to processing.
App and files are on a Linux system (CentOS). App is in C. Machine is controlled by a third party.
What encryption libraries would you recommend? And, is there any clever way of managing the decryption key beyond compiling it in the code and doing some basic obfuscation?
Are they fancy obfuscation libraries out there, for example?
And, the reason I'm not going to SO (well, one reason) is that I don't want to have 50 answers that tell me that's it's impossible to 100% protect data on a machine you don't control. This I understand---just looking for "best effort" solution.8 -
JFrog Artifactory uses HTTP POST for updating and HTTP PUT for creating.
... I'm correct to be offended by this yes?2 -
For every verb you put in your 'REST' api url, a puppy dies
Bitches be saying they're using REST and don't have a fucking clue what it means or what the principles are5 -
I recently built a Mock JSON based REST server, that can help you out with API testing and prototyping without having to write any code for the backend, feel free to try it out, and star the repository if you liked it :)
Link: https://github.com/ishank-dev/...3 -
Public REST (-inspired) API. Should I skip numeric IDs because it's easy for consumers to snoop around?
Example:
POST api/foo
201 Created api/foo/69
Uh, I'll get 68 just because I can. Hopefully it returns Unauthorized, unless we some kind of bug.
Is it just security by obscurity if I use, like, guids or something instead of sequental IDs?17 -
Reading a 36 page article on REST for a course on OSS, and I'm pretty sure the combination of background sound generators (waves, fire, singing bowl, cat purrs) is what's going to get me through this exam...
PS: Recommend http://purrli.com for all demotivated, cat-deprived devs out there.2 -
Just implemented a feature using Builder pattern .
State of mind : aaaghh fuck this shit , i am in hell . let's get some rest before integrating and testing this disaster
after some rest , while integrating " Oh you beauty my past self, i love you😍😍😍😍 -
RESTful API Question
Let's say when a user do an action, I need to insert a record into a table and then update a record in different table.
Should I write two API routes (PUT, POST) or one route (POST) ?18 -
REST service documentation translated in italian language.
"arricciare" => curl
"biscotto" => cookie1 -
Fuck api docs which are blatantly wrong. Wasted several hours on building an API client with pagination according to the api docs.
Turns out the actual implementation did not follow its own spec / api doc and returns values without pagination. And some objects are not objects but arrays.
I mean, next time I build an API client, I'll just fire a dozen requests on the endpoint, see what it wants and see what I get and maybe guess right what it actually does.4 -
Rest API not working since yesterday
:( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :(5 -
I hate discussions about how to name resources in a REST api. It’s not like there will ever exist a client that magically knows your conventions. At some point, you need to hardcode an URL in a client/browser. That’s fine, just keep it simple.
This has been a great source of bike-shedding in my job recently.
And don’t even get me started on HATEAOS...2 -
So this is my first experience of shitty code written by colleague
God, for REST API she used ?id=<int>
Not only that,
if the route was /cms
she used GET method for /cms/get/?id= to get single record and
/cms/getAll again in GET method to get all records
Damn15 -
16 files (!) to create a rest endpoint that does nothing (returns an empty wrapper message).
WTF spryker? are you fucking kidding me?5 -
Developed a very simple REST api with pure php. Eventually "api/users/" worked but "api/users" was 301 moved!!.. it was a big problem1
-
Spent the day refactoring a REST app into graphQL, that feeling when all tests are green and everything is committed and merged 😧🤓3
-
!rant
I will have almost 3 weeks of vacations coming up. For which I will TRY and understand the idea behind building a REST API using the Microsoft C++ cpprestsdk libraries.
The end goal? Be able to replicate a little project I got going in Node.js in order to compare how well it goes on C++, a language that I greatly fear on accord with how complex the syntax always looked to me :V The thing is, the first time I tried to learn programming was when I was about 17 and c++ was back then not the way to go for me. I sometimes wish I would have stuck to it, I k now enough to get by building and linking shit correctly, and of course the basic concepts are there, some advanced ideas are iffy but I should be able to get them going relatively well once I start working on the code.
I am using this tutorial as a basic guideline :D
https://medium.com/audelabs/...
Will be interesting to see. Always wanted to have something done with C or C++ that was bigger than any of my academic projects. Funny enough, I have a large collection of C++ books, but never really used them since they would bore me :V
Cheers putos! -
In Django code, looking at a class for caching REST calls. The cache is using Redis via Django's cache layer. In order to store different sets of parameters, each endpoint gets a "master" cache, that lists the other Redis keys, so they can be deleted when evicting the cache. Something isn't right, though. The cache has steadily increased in size and slowed down since 2014 even though many events clear the whole thing!
... And then it hit me. Nothing empties the list of cache keys. Nothing. So it has been growing endlessly since 2014. And everytime it grows, cache eviction gets a little more expensive, network traffic increases a little more, and cache evictions get a little slower.
Fixing this bug took things that were taking routinely an entire minute to complete and made them take a couple seconds. -
I'm writing a blog series about GoLang and REST interfaces, if your interested in golang but don't know where to start give it a read https://blog.mescrocker.co.uk/golan...2
-
Can't decide if I should join this nice internship or let myself enjoy this summer and rest a bit, as I burned out a bit this semester with studying and freelancing.
Why is it so difficult to decide..
The internship is at cool place with nice tech and I feel like its a nice opportunity to grab, but I feel like I need the rest too.
And I have to decide tomorrow. I guess I'm terrible at decision-making sometimes Ffs..3 -
That moment when you have to exchange data with another system using XML-Files serval hundred MBs in size instead of a proper REST API (ノಠ益ಠ)ノ彡┻━┻7
-
Thank you for the 20-20-20(6) rule.
I think I read about it here, I don't know if it helps but I do feel better.
I recommend it.13 -
rant == false && help == true
I usually don't like posting non rant stuff here but I need help.
How do you usually design your service communication class?
I am working on a mobile app which contains talking to a REST service, I usually put all network calls in one class. Down side if it becomes a big class it becomes a pain to maintain. Any thoughts?
For a backend service I usually go with Repository design and it is working out well for me. But for mobile Apps I'd like to see if there is a better approach4 -
> be me, associate dev
> slack mid-level dev 40 lines of code
> I have never written a REST api before
> his response is "lol"3 -
APIs, APIs, APIs... I feel like building an API for everything which goes over the wire is a must-have today! Yes it makes sense for decoupling purpose, access control etc (all the things we learned from OOP design principle books when we were in school) but come on, REST API for internal database access when there is something like SQL over JDBC/ODBC/WhateverBC ?? So I have to study the REST API documentation for applying simple where-statements but in API manner...4
-
I been using digital ocean to host my server for a project, but they seem to get shutdown because of DoS behaviour. I have no idea why. The server is doing some soap and rest communication and controlling a database.
To be fair the password was poor, but it was meant to be a fast way for four people to work on it at the same time.
But after the first shutdown, we rebuild the server and work on functions. Finish the work and went home. But in the server 9 hours of uptime with 2 of them unsupervised it was detected as DoS behaving server.
💻🔪2 -
Thanks for nothing, Insomnia REST. Everyone using it beware: turn off auto update, version 8.0 will look you out of your projects unless you create an account with them.
Get fucked.4 -
This morning me and my colleague had huge debate about using GraphQL or REST. While I was in total favour of GraphQL, that guy was more on REST side because he read some random articles on dev.to and medium and was highly motivated to use REST instead of GraphQL.
The problem is, some people write anything on blogging websites without even doing a proper research.
Since, I have worked on GraphQL, I knew it's pros and cons very clearly and what are the things that can be done to solve them.
The guys said that we can't do native caching in GraphQL at which the lava from my head just got burst out.
I showed him the official GraphQL docs where it was clearly mentioned that we can do caching in GraphQL.
Poor guy couldn't say anything after that.
P.s: We are still going to use old school REST APIs but I am happy that I could prove my point. I'll use GraphQL in my side projects anyway, loss for him if he's not exploring something new.7 -
Currently we have to make a new REST API at work. I want to have a clear and functional API (with HAL JSON, that is given). But my colleagues don’t like this, because they don’t like the design (the look and feel) of the HAL JSON responses. They just want an easy API with a nice design, so they want to ignore half of the HAL JSON specification. But a REST API don’t has to be easy and don’t need a fancy design, REST APIs are not for humans but for computers! How can I explain this to them?3
-
Should I reproach my teacher for not being able to teach REST properly? Everyone in my course think REST endpoints must be UpperCase. Also, he keeps saying to use Git but in the end he's currently using PDFs to send sample code.3
-
Soon I’ll be unemployed (on purpose) and will spend some time on my own project ideas.
Pretty much each of them will require an API..
Already started with the first one using python + flask, but I’m planning to do each of them in a different language..
What do you propose? What’s the most fun and the most interesting technology in your opinion?
I’m senior in Java and advanced in JS, / Node so it won’t be any of those and I’m also not a fan of PHP :)5 -
Who in their right mind would do this / think of this....
Salesforce has the option use their API. Either via SOAP or Rest. At my work we currently use SOAP and I wanted to rewrite that to Rest. Fine, you would say.
Their Rest API uses oAuth, nothing fancy you would think. But those motherfuckers, per default have the option enabled that the refresh tokens you get via the necessary API calls are being marked expired the moment the API gives them to you... Then why the hell give them in the first place.
It took me 2 hours of my life to figure out, why in godsname all my refresh tokens were marked as expired. Fuck you Salesforce, I want those 2 hours back! God fucking damn it... I really fed up with this type of bullshit!! -
For a new microservice we were designing, I recently had a design discussion with a team member on creating REST endpoints for a new entity. This discussion went on for almost 3 hours, most of the time was spent on why to have two endpoints for getting this resource, one is a POST using a graphQL-like query and another one is a GET using unique ID. I said, the client-side use case is different, one is a dashboard where search results need to be shown based on multiple fields and the unique ID won't be available there because it is a system generated value, second one will be used when the unique ID is present in the client as a result of previous search result. Their responses will be similar, first returns a list of entities, second returns a single entity of the same structure.
Then came the next argument: if both APIs are returning same response, why do we need two different requests ?
It was like saying, because 5+6=11, any sum of two numbers resulting in 11 should always use 5 & 6.
Are people so frustrated of working remotely all the time that they come with such weird arguments ?1 -
!not a rant
Peeps using Postman - Check out Insomnia.rest it looks awesome
https://insomnia.rest/
PS: Think it's built with Electron.10 -
Friday: I have done a lot of work this week... Should take rest in the weekend
Saturday: Who needs rest? Let's learn new hobbies, watch movies, play games and have fun🤩
Sunday: I think I will take some rest today...But that series is so cool...
Monday Morning: Why did not I take sufficient rest the whole weekend 🥱🤦🏽♂️
Monday Afternoon: Slept for two hours in the office time😑2 -
Does anyone know why websockets aren't used far and wide for APIs? I mean not like chat applications, but the typical webapp, say an online shop. For me it seems kinda wasteful to fire separate requests with tiny payloads all the time. I currently use moleculer and socketio for a quite big project with multiple websites and backend containers, and so far, i haven't found a disadvantage.
So what have i missed?12 -
Wrote another post on medium.
This one helps in automating the security token required for testing an API.
https://medium.com/@gvnix/... -
Was so angry... Was all the day wondering why my rest method wasnt outputting a certain property (in null to be more precise)... When almost 5 hours has passed, I realized it was due the @JsonIgnore annotation... soooo angryyyyy jaja
-
When I was working on my dissertation project. I was implementing a video sharing platform. Using Dropwizard for REST. I wrote the entire endpoint for uploading a video in one session. I was just taking a stab at how i thought it could work. Tested it in Postman expecting to get some kind of error.
And it worked first time. -
Have a SOAP service but need REST service since it is in fashion?
Easy, make a endpoint and ask for the entire body of soap (yes, in xml) in body of rest request.8 -
Spent 3 days in a santorium. With my fam.
Didn't rest a bit [with temporary exceptions of evenenings where I did get to relax in a steam bath [50C, 99%] followed by ice cold water bucket].
Not looking forward for the monday. At all.2 -
GraphQL or REST?
I'm not really worried about boilerplate (my research reveals it's roughly the same), I currently have a (very incomplete) REST interface, but that was just for testing.
Also, the API has no real usage yet (I only use it for submissions) and it literally exists for the sake of having an API (so I don't need to write it later).10 -
While working with Django Rest Framework, the Post and Delete requests were giving me 403 error. With no help from stack overflow, I decided in vain to check it with Firefox browser instead of Chrome.
IT FUCKING WORKS ON FIREFOX!! HOW THE FUCK??
Things like this are responsible for my mid life crisis.12 -
it's a bit annoying when you, as a consumer, have to rev-engineer the temporal coupling among dozens of rest methods.
It's not fun. NOT fun at all2 -
Question.. architecting a large system. I’ve broken it down to microservices for the DB and rest API / gateway
I want there to be some some processes that run continuously not event driven via rest. Say analytics for example what is the best way todo that? Just another service running on on a server? And said service has its own API? That when the other rest APIs are called could then hop and call the new service?
Or say we had a PDF upload via rest should that service then do the parsing before uploading to DB .. or should the rest api that does the uploading then call another rest api to another service dedicated todo the parsing and uploading to the db?
I think the bigger way to explain the question is the encapsulation between DAL.. data access layer which I have existing.. but then there’s the BLL .. buisness logic layer which I don’t know if it should have its own APIs via own microservices running in the background.10 -
Hey guys, who has experience with JPA/hibernate RESTful performance numbers.
Interesting would be:
* persistence operations per second, and the response times
* proportion between read/write for a typical rest service
Rightnow i get ~300ms read, 900ms write at 350 concurrent requests. 75% write operations
I more or less ruled out my custom code, problem seems to be hibernate (of course ...😋)
Stack: jetty, jackson, hibernate, mysql9 -
// !rant
Need some assistance with Drupal and Dreamfactory.
Dreamfactory is an amazing piece of software that basically turns any database into a REST API. I mean any DB from SQL Server to MySQL and all kinds of others. For a connection to the API it uses JWT (JSON Web Tokens) which expire momentarily.
On Drupal, there's wsdata and rest client modules. Restclient is a module where you configure a connection via OAuth or HybridAuth to a rest server. The problem is that the rest server for dreamfactory uses JWT and i'm not sure how to get Drupal and restclient to connect that way. -
I recently built an automated payout functionality for bank-to-bank transfers, and we initially looked at using the pain.001 XML schema to do it. Luckily, we ended up finding a service that has a simple REST API to do this instead. (Thank god we didn't go with the XML method, I know how much of a headache that could become, I can imagine the treasure trove of memes with naming an XML schema with the name PAIN)
Anyway, for one of our big-brained product managers, this will forever be the infamous "XML Task" that he continues to ask about and bring up. I've already clarified a few times that we have long chosen a solution process that has nothing to do with XML, but to no avail, it will forever be his "XML Task". Wonder what name he'll pick next time we need XML in a solution? "Second XML Task?" Let's just keep the mental overhead idiot train going!2 -
"It's just as easy to create a small REST microservice as there is for a small one-off script, so let's follow the design pattern of creating a REST service first."
I don't think my manager understands how different in complexity these two things are.1 -
The moment I turn off my laptop in anticipation of an hour or two of recreational YouTube binging and then rest
- my Bluetooth headphones run out of juice, courtesy of over 12 hours of semi-constant usage and the fact that I didn't think to charge them overnight
- In a moment of perspective change I instantly realize how to solve the problem I've been struggling with for the past 3 hours, ensuring that I'll keep thinking of work for the following 5 too.rant inspiration built-in batteries bad luck artificial downtime perspective change work-life ramp rest9 -
So I've been reading about rest api and I purpose there should be a standardized keyword for message
like 'errorMsg', 'msg', or just 'message'
I m kind of tired of discovering new acronym for error message or message every time I write a REST service3 -
trying for three hours to understand why an error occurs. adding one log statement. reloading. everything works... 😡3
-
Requested latest code from TFS server ... there goes the rest of my afternoon. 26 Errors, 470 warnings.
-
Wanted to add a simple log entry when a model changes state in a certain way.
Unit tests pass, functional tests pass, manual tests through application GUI pass.
But for some fucking reason the single line logging call I added results in an error 500 when the application is accessed through a REST API.
Going to have a fun day tomorrow debugging this shit. -
When did we decide managing Users through Cloud REST architecture was more secure than having them in an underlying DB?
Because I can't put my finger on exactly why... but I don't like it and I think it's probably less secure... and just spawned from the need to be able to make user management a subscription based service like fucking everything? When a simple MySQL or postgres and some bcrypt somewhere would be both more secure and infinitely cheaper?
I'm more used to consuming REST API's than writing them. Can any you REST peeps help me understand how a REST API could be made as secure as a SQL DB connection for user management?
What do you think the attack vectors are for a REST API User Management? Like... what's the SQL injection of REST API? Pack some extra JSON somewhere or something?
At least if I can have faith my shit's not gonna get hacked because I have to use a 3rd party REST service for User Management of Users to my own fucking app I can maybe sleep tonight.2 -
hello folks, any help would appreciated :). serious question about designing/developing a rest backend.
here is a little insight: I want to reduce the endpoints for many CRUD operations as I can. So for that approach I defined a set of "dynamic" routes like /:moduleName/list, /:moduleName/update and so on.
Now I want to also reduce hardcoding as much stuff as I can for the front end. like I want forms/view/components to know which fields can be sent in the "/:moduleName/xxx" endpoints from above. So I'm thinking to make some /:moduleName/list/map, /:moduleName/update/map endpoints that tells the frontend which fields/keys can be sent for X or Y operation.
regarding design/security concerns Is that a good approach? do you know any other approach that's like to what I want to achieve?6 -
I want to build my own REST NET API, I am familiar with C#. And I was working with Flask, Django and Express.js
The whole webapi structure of dotnet project seems to me a bit strange. Do you have any favourite resources that helped you to get into dotnet?6 -
This is not a rant. Rather just a question or an ask for advice, as I have seen a lot of people talk about web development around here. I am planning to create a website for my search engine. I created a Rest API for my VPS so I can do http requests and retrieve some links for certain key words. But I need some good ideas to do this from a website. As I am not sure what would be the best way to do http requests. As far as I know it's possible with Js and PHP, but I am not sure what's better, more secure or convenient? So here I am to ask you guys, especially those who have experience with this, what I should consider to do.
Oh and please forgive me my limited knowledge about Js and PHP 😅😊3 -
I need to build a REST API in PHP, what framework could you recommend me?
Lumen (https://lumen.laravel.com) looks fast and relatively simple.
has anyone ever used Api Platform? (https://api-platform.com) What are your thoughts on it?9 -
Today i present GraphQL to my colleagues.
Tell me your experiences with "querying your REST endpoints!2 -
Is there a Java libary or a list of the endpoints that devrant uses? Would like to write my own client2
-
Hi, I hope that you guys can help me : Is Django REST Framework valuable for developing a little-sized android app backend? Does it have any support/community?
Is it better to just Django instead?12 -
Question.
I have a java app to monitor and send aprox every 3seconds a json with data to a client who will present it on a single fancy display, there will not be other clients ever, only this single one. Shall I go websockets and push the data, and wait for it there or shall I go rest and ask for the data every 3 seconds? Im planning to use node on the client regardless of the solution. ?7 -
Sooo i made this program that uses both chromium but also is a rest server. (they need to be together for this program)
Soo the rest server requieres to be run with sudo
But the chromium Browser must not. It says must provide --no sandbox (to run as sudo)
so then i added --no sandbox
and it works like i wanted it.
However every application seems to be glitching sometimes (only ui) but no lag etc.
How can i stop it from glitching :0 i mean it does work though13 -
!rant
Got a question since I've been working with ancient web technologies for the most part.
How should you handle web request authorization in a React app + Rest API?
Should you create a custom service returning to react app what the user authenticated with a token has access to and create GUI based on that kind of single pre other components response?
Should you just create the react app with components handling the requests and render based on access granted/denied from specific requests?
Or something else altogether? The app will be huge since It's a rewrite off already existing service with 2500 entities and a lot of different access levels and object ownerships. Some pages could easily reach double digits requests if done with per object authorization so I'm not quite sure how to proceed and would prefer not to fuck it up from the get go and everyone on the team has little to no experience with seperated frontend/backend logic.4 -
When starting a new project, is it still best to use Rest API than GraphQL?
Most big enterprise companies use Rest API.9 -
It seems odd that in a world where Web developers are mostly developing api first there are no tools that allow you to browse an unfinished but already authenticated REST api.
I would really like to have one but programming a full IDE/Project manager sounds like too big of a project.6 -
When your business processes just don't map to four HTTP verbs, and the world seems a little less well-ordered. That feeling.
-
Help needed.
Anyone who has worked with OpenBazaar REST APIs. I cannot seem to get any response from the endpoints even though I think I've set the server correct. Any sort of help would be highly appreciated.
P.S. (Rant) the docs and the "helpful slack community" are total shit. -
Does anyone know of any good examples of server and client implementations of a java rest service using cxf and multipart content?
-
Someone else had to work with that turd of WSO2 Enterprise Service Bus?
I hate everything of it: its fucking buggy IDE (a lazy fork of Eclipse in which they didn't even bothered to replace the Eclipse icon), its cryptic XML language which makes basic operations such as accessing a JSON field a complete PITA, its fragility (often syntax errors doesn't get caught by the compiler but causes runtime errors which are hard to diagnose) its shitty testability...1 -
I'm building a nodejs REST api with jwt token authentication for the first time. So far, it's been as smooth as butter. Any hiccups or gotchas I should worry about?
-
Slept for 4 hours after 10 hours programming session and I still feel pretty good.
Does that mean that code == rest? Woops!1 -
What HTTP Header should be used to send an App identifier to a REST/micro-service
I remember reading about this a long time ago and want to suggest it again to my boss so it's easier to identify what specific apps making calls to our APIs3 -
All the microservices are planning to communicate via kafka. And they are planning to put a REST API between kafka and the service. So all services hit the REST API with the events and the REST API send events to kafka.
I don't see any benefit of having a REST API between the service and kafka. What are the opinions in the wild?12 -
First contact with XEN.
Xen Orchestrator UI / Web, logged in first time...
Wow. The UI is a big giant mess...
I don't care for this fucking bling bling shit... Need to have an overview of all VMs.
Oh Lord... Wtf... Icon hell...
Hm, I need more detailed information... Ah. Found the button.
Pressed button.
Wtf... What's taking so long...
Bloody shit.... Why does it include real data diagrams of usage statistic per row????!!! (had pagination set to 100 rows, one row is one VM)...
Bloody christ, ain't no option to configure that monstrosity... Export function?... Nope... Great. This will be a giant fuckfest...
Rest API? Nope.... Non existent as it seems. Thought that would be common in the 21st century... Guess what, nope.
Further googling...
Oh interesting. An cli client in NPM?
Hm, pretty scarce documentation...
Poked it a bit... Got first results...
xo-cli --list-objects type=VM
...
Let's take a look...
Oh JSON. Gooooooo(d)....
Wow. The document structure looks like someone puked out alphabet soup...
Or maybe the dev had hemorrhagic fever and was suffering from delusion and blood loss.
After this... More than devastating experience...
I took a look at Proxmox REST API.
Sweet jesus. That's like... Stone Age to 23rd century. Oo
https://pve.proxmox.com/pve-docs/...
Seriously... It seems not so hard to define an API to get the data of all VMs... Without suffering a traumatic brain injury.1 -
Question:
First big app around the corner. The backend is a REST api in pure php.
I've heard of heroku and other alikes but never had any time to look at it. Would any service like this benefit me?1 -
My first experience with a computer was inhereting my older brothers Amiga 500. The rest is history!
-
Crush is lyk theoretical algorithms. Just good to thing about. But implementation ... U knw rest of it.
-
Can you suugest some Project for Web development that can help to clear my fundamentals and also help to learn advanced technologies in this domain4
-
You know that your are working with a DB-Guy when he provides you a "REST" interface that is outputting table data in JSON format and not even the JSON syntax is correct.
-
I am developing a webapp with a couple of friends and we want to implement stripe API with Django Rest. Does anybody knows about good integration test packages/practice that could be useful in this case?
-
So I want to start with rest API development in Spring Boot. Where's a great place for 'all-you-need-to-know' related to Spring? I already built other REST API's so I just need a quick getting started and know how to organise,configure etc. my java project.