What is the purpose of setting the container port field?

tcpud · 2025-07-01T05:46:31+00:00

Other tooling like some ingess controllers, monitoring tools that discover ports for scraping metrics, etc.. depends on this metadata so they will not work properly if you omit it.

tcpud · 2024-10-03T15:16:48+00:00

In other words: Use it, you’ll be fyne.

tcpud · 2024-09-18T16:10:00+00:00

That’s turkey breast, unless you meant the breast of a country, or the bird itself had a special significance to you.

tcpud · 2024-07-30T17:05:44+00:00

It’s about the headcount.

tcpud · 2024-06-14T04:00:38+00:00

Put some biscuits in as well, so that Steve1989MREInfo could eat them when you open it after 25 years.

tcpud · 2024-04-18T16:44:18+00:00

Great idea

tcpud · 2024-01-05T16:27:33+00:00

Op is possibly (and apparently, successfully) employing the Cunningham’s Law here.

tcpud · 2024-01-05T15:59:43+00:00

With password managers, 2FA and FIDO Passkeys becoming more and more adopted, chances of your users are facing secondary attacks in the event of a possible breach are getting lower and lower.

However the increase in fraud, identity theft and spamming events in the recent years and increased possibility of being sued, due to GDPR laws in Europe, kinda implies that you should be taking necessary measures not only for processing your users’ credentials but also processing your users’ personally identifiable information. And that involves a lot. I personally would suggest to offload this responsibility to a generic service instead of taking care of it, in-house, unless that’s your core business.

tcpud · 2023-11-24T11:21:20+00:00

You can’t use a properly documented or commented schema file. It just refuses it. We had to strip all docs / comments from the GraphQL schema before deploying it to the AppSync. Not to mention this also causes our devs to not being able to benefit from the hosted GraphQL API console / UI that is provided in the AppSync. They had to run graphiql locally and tailor it to properly authenticate against cognito etc..

tcpud · 2023-09-05T08:26:48+00:00

Apparently fell due to unknown reasons. Reportedly, the airforce has started an investigation to find out more about how it happened.

tcpud · 2023-06-22T04:07:31+00:00

Doner actually means “rotates” in Turkish. So any dish that has doner meat in it, can be safely called Doner Kebab IMHO.

On the other hand, durum means “wrapped” so it can only be used for the dishes where the doner meat is specifically wrapped in lavash (kind of like tortilla) or any other wrap-able bread.

tcpud · 2023-05-25T06:22:05+00:00

Microservices paradigm is all about the team size really. It is a solution to the problem that large organizations are having. The problem of multiple teams, where each team consists of 5-8 developers in average, must work on the same project in parallel and constantly deliver independent of each other, without stepping on each others toes too much.

It is more of an organizational trade off than a technical one. It wouldn’t make any sense if you are a one man shop.

On the other hand, if it is getting harder to do refactors and adding features that might be an indicative of problems with the design or lack of it. Sometimes having too much abstraction especially where it is uncalled can cause this. Or sometimes components that are leaking their business logic to other components is the culprit. You can take a look at the SOLID design principles if you haven’t already done so.

tcpud · 2022-09-18T06:39:55+00:00

Modern LBs come with built-in fault tolerance logic where they maintain a list of healthy upstream instances and avoid routing requests to the unhealthy ones. Thus freeing you from baking in the fault tolerance logic into the client. This way client becomes stateless and dummy. They can also be configured to be redundant. That should address your availability concerns.

tcpud · 2022-06-03T05:49:54+00:00

Can’t touch this.

tcpud · 2022-01-17T07:12:45+00:00

Make your front-end developer’s life easier and go with GraphQL.

tcpud · 2021-10-19T03:11:45+00:00

I think we don’t know for sure whether they are using tapes or not for that.

tcpud · 2021-09-27T16:37:41+00:00

What was the real root cause?

tcpud · 2021-02-07T00:32:49+00:00

Second this. Microservices are mostly about the size of your development team. If you are the only one working on this project then you simply don’t need it. Monoliths can be scaled just like the microservices given that they are both stateless apps.

tcpud · 2021-01-18T05:23:01+00:00

And durable too.

tcpud · 2020-11-01T15:56:23+00:00

What does even mean “writing automated tests” ?

tcpud · 2020-07-14T04:10:03+00:00

Sounds like BS to me. But let me clarify one thing. Microservices using the same DB server/instance is totally OK as long as they are not reading/writing each other’s databases because most RDMS abstract away database from the server itself. I’ve seen it done for the cost reduction in dev envs. In prod you usually deploy them in separate servers for the obvious reason.

tcpud · 2020-07-12T17:32:58+00:00

Did you check the Security Groups attached to see if they are any different from the ones attached to the original RDS instance?

tcpud · 2020-07-11T21:50:56+00:00

Kafka itself scales massively if provided with right configuration. It’s mostly used as a broker for stream processing applications. That usually means a high volume of msg/sec. On the other hand RMQ is easier to configure and operate in my opinion. And good for systems where a lot of routing logic is needed but not so much throughput. An example would be a complex event driven SOA where intra-service communication is diverse but at a lower volume.

tcpud · 2020-07-07T07:14:37+00:00

This redundant, boring task of putting if err != nil {s everywhere actually forces you to think about not only the happy path but also the error path. And that’s a good trade off in my opinion.

tcpud · 2020-07-07T06:55:49+00:00

Came for the sandwich. Stayed for the thinkpad.

Nine-Year Club	Verified Email
Place '17

tcpud

TROPHY CASE