Fern (YC W23)’s Post

If you're struggling to implement Serverless Architecture, this is for you. Dante Faña, our Director of Software Engineering & QA, explores key considerations including resource management, artifact weight, service quotas, and code sharing between Lambdas. Gain valuable insights to overcome challenges and make informed decisions for your next project. Read the post here ➡️ https://lnkd.in/ezAFdqRx #GBH #ServerlessArchitecture #Articles #ExecutiveInsights #SoftwareDevelopment

Just when you thought the API spec wars were over - new entrants like AsyncAPI have burst onto the scene. Choosing the right API definition format is crucial as it affects your choices in frameworks, tooling, and documentation platform. Learn more here: https://hubs.li/Q02Rncr70

Hi there connections, I am thrilled to share that "Alhamdulillah" i have just recently completed a personal backend project of my own all by myself, there was so much learning in this project. It is a Microservice architecture end to end backend for Bus Trips and Ticket Booking system. This project is basically for my learning and knowing nuances of Micro Service architectures. I request everyone to go and read the 4th page 3rd para(Seat Mapping) of the documentations , there i discussed a problem with my version of solution and i want to learn how you guys handle this kind of problem. search-service-github - https://lnkd.in/giYhRiuE booking-service-github - https://lnkd.in/gz_bPngN Api-gateway-service-github - https://lnkd.in/gjEPe3S6

Just finished the course “Building APIs with Swagger and the OpenAPI Specification” by Kevin Bowersox! Check it out: https://lnkd.in/dcG5QMaw #apidevelopment #openapispecification.

Just finished the course “Building APIs with Swagger and the OpenAPI Specification” by Kevin Bowersox! Check it out: https://lnkd.in/ew6F5D86 #apidevelopment #openapispecification.

#lowcodenocode I would have liked to attend this seminar linked below to hear more on the topic. With that said, let me add my own thoughts on this: As much as we talk about low-code/no-code, there continue to be hurdles to overcome. Let me give you three main points to consider: 1. Limitations ========= Much of the low-code/no-code tools that non-programmers use have their limitations. Even as a business user, it's good to do some research to find out what these limitations are. 2. Gotchas ======= Let's suppose you want to create a small app for yourself that suits some particular purpose. Some of these tools aren't necessarily that easy to learn. Nor do they allow the same flexibility a person tends to have when they have full programming tools. As a busy person, just try to understand how much time you really want to spend on this and whether you have any chance of achieving what you're trying to get out of this. 3. Opportunities =========== Beyond that, if you do build something that is partly helpful but where it would be most helpful if you got someone to write just a tiny bit of code for you to add to it, that is also useful to know. If you can create something that gets you partly there and maximizes your small budget to allow the final bit to be developed elsewhere, that is another useful way to look at this. Finally ===== As usual, I just want to ask you to be a little skeptical of the grand claims of some of these tools and also to know that the full versions are not necessarily what you have. Read and prototype (I mean that you should try it out rather than believing what you read or hear) all of the major features with skepticism until you know for a fact that you do have access to the ones you need.

Just finished the course “Building APIs with Swagger and the OpenAPI Specification” by Kevin Bowersox! Check it out: https://lnkd.in/ex7p_VMv #apidevelopment #openapispecification.

I had the opportunity to attend the introductory session of the 30 days Back-End Workshop conducted by Prince Kumar Singh On the first day we discussed about APIs,Role of API and how it's used as a middleman between service provider and clients,how back-end code is written in production and setting the agenda for the workshop. I am excited for the upcoming lectures and doing a deep dive on back-end technologies. #LearninPublic #WebDevelopment

Just finished the course “Building APIs with Swagger and the OpenAPI Specification” by Kevin Bowersox! Check it out: https://lnkd.in/gSrri93T #apidevelopment #openapispecification.

What does code written in Modular Monolith architecture actually look like? With Spring Boot and DDD, we set out on a journey of writing maintainable and evolvable code. The term “Modular Monolith” has been going around a lot recently — especially as an alternative to Microservices which is no longer a default choice when building new applications. But what is exactly meant by writing modular code? Is it about organizing code in a certain way? Is it about following certain architecture styles like Hexagonal, Onion, Clean etc? What does a codebase written in the modular monolith way look like?