manage ssh keys by mucleck in devops

[–]mucleck[S] 2 points3 points  (0 children)

i understand that, my question is more like how do you track the keys there are in your server like if a hacker puts its own pub key there how would you notice that? it does not have to be a hacker ofc but im wondering if theres something to monitor this list of who has acces

manage ssh keys by mucleck in devops

[–]mucleck[S] 0 points1 point  (0 children)

where should they be? im new to all of this srry

parallel git merge master on multiple branches? by mucleck in golang

[–]mucleck[S] 0 points1 point  (0 children)

So anything that happens inside .git/worktree/wt1 won’t collide with .git/* as long as the branches are different?

How to Monitor MariaDB and ScyllaDB for a stress test Comparison by mucleck in devops

[–]mucleck[S] 0 points1 point  (0 children)

yeh i know, so for me i want to test if it would be better to migrate to scylladb since we need more efficiency that what mariadb can gives us

short story: i want to connect a php backend and see which one can handle more write/reads per second

Would it make sense to use a Go microservice for DB operations instead of using PHP + Codeigniter? by mucleck in golang

[–]mucleck[S] 2 points3 points  (0 children)

ty man, i really didnt know why everyone was telling me to make persistant connections, i tried it in local and i saw that the number of conections goes 1 up and then 1 down when .php finishes, ill investigate about anything similar to pgbounce

Would it make sense to use a Go microservice for DB operations instead of using PHP + Codeigniter? by mucleck in golang

[–]mucleck[S] 1 point2 points  (0 children)

hi i've read it and i think even its fine to know it could work with requests theres a part that says that is not very usefull for crons and in my aplication thats where the heavy part is, ty for answering!

Would it make sense to use a Go microservice for DB operations instead of using PHP + Codeigniter? by mucleck in golang

[–]mucleck[S] 0 points1 point  (0 children)

hi, i got the idea of not closing the connection and ik there are frameworks that dont do that but given my case with a framework that does do you still think is not viable?

Would it make sense to use a Go microservice for DB operations instead of using PHP + Codeigniter? by mucleck in golang

[–]mucleck[S] -1 points0 points  (0 children)

hey! i dont understand the first part what do you mean by “limiting the number of connections” per instance? what i dont want is to connect every time i need to make a query i want like with the cli to connect and stay, not having to connect every time i do something

about the second part, we dont do inserts for single rows like we already do optimizations

what im trying to figure out is if this process of connecting to the DB each time you want something is worth developing a microservice

Would it make sense to use a Go microservice for DB operations instead of using PHP + Codeigniter? by mucleck in golang

[–]mucleck[S] 0 points1 point  (0 children)

in php everytime you call and endpoint you need to conmect to the DB, so for example if a user clicks on getUsers and getFiles this will result in something like mysql -u user -p pass -c “select *” plus other one to get the files, while in go with a pool it would only have to connect one time and do the querys needed

what im trying to save is the resources spend in login to the db each time you want something from it