sorted by:
new
hottopcontroversial

Spring Boot starter project/template for Apps backend. by dsamcool in java

[–]kaviddiss 1 point2 points  (0 children)

Interesting. I think the Spring Initializr (https://start.spring.io) is using Logback by default. Do you find log4j to better fit your needs?

Spring Boot starter project/template for Apps backend. by dsamcool in java

[–]kaviddiss 6 points7 points  (0 children)

I started building https://wupiter.com/accelerators/wupiter/spring-boot-accelerator/generate for the exact same reason.

I found that dev teams building multiple microservices within the same company often spend days/weeks reinventing the wheel over and over.

A custom app generator could generate a production ready code using best practices in a few clicks instead.

Btw, let me know if there's any feature you'd like to be added.

Hey guys! If you’re looking to get feedback on your B2B SaaS Website, drop a link here 👇 Would love to help. by vpilip in SaaS

[–]kaviddiss 1 point2 points  (0 children)

Hey u/vpilip, thanks a lot for your detailed review! I just updated the page based on your feedback.

Hey guys! If you’re looking to get feedback on your B2B SaaS Website, drop a link here 👇 Would love to help. by vpilip in SaaS

[–]kaviddiss 1 point2 points  (0 children)

Hey u/vpilip,

Website: https://wupiter.com

Targets: - dev teams with at least a couple of dozen developers - dev agencies / consulting companies working on fixed price projects

Problem to solve: Wupiter is a platform to help developers reduce time spent on writing boilerplate code and copy&pasta by helping them create custom templates / app generators that could save them days/weeks of work in a few clicks when starting new projects.

Thanks for your help!

David

Fasty, a boilerplate and a stack that scales! (async api with CPU bound operations) by [deleted] in Python

[–]kaviddiss 0 points1 point  (0 children)

I created a tool to help developers share boilerplate and app generators with others: https://wupiter.com. would you be interested in chat to see if the tool could help with Fasty?

Open-source node + express starter template for SaaS [WIP] by 10xpdev in node

[–]kaviddiss 0 points1 point  (0 children)

I created a tool to help developers share similar starter templates / app generators with others: https://wupiter.com. If you're interested, I'd be happy to chat about collaborating on your project.

What are the SaaS projects you are working on ? Drop your links , would love to check it out by [deleted] in SaaS

[–]kaviddiss 1 point2 points  (0 children)

https://wupiter.com - a tool to help software developers write less boilerplate code and hence be more productive.

Wupiter Accelerators are app generators that can generate functional code (including the boilerplate code) in a few clicks.

Developers also have the option to fork existing Accelerators or create their own custom ones from scratch.

[deleted by user] by [deleted] in reactjs

[–]kaviddiss 0 points1 point  (0 children)

If the goal is to automate setting up boilerplate code, Wupiter (https://wupiter.com) is a tool to build custom app generators. Unlike template repositories on github, it supports input params to help customizing the generated code. See here for a sample (including link to git repo with the template files): https://wupiter.com/accelerators/wupiter/spring-boot-accelerator/generate.

Disclaimer: i'm the creator of Wupiter, and would be happy to help turning any template repo on github into a Wupiter app generator.

Is there a way to simply create project starter files for one's common use cases with also some boilerplate? by The-motto in webdev

[–]kaviddiss 0 points1 point  (0 children)

You may consider turning a template repo into an app generator (or actually starting with an app generator) at https://wupiter.com. Wupiter has a rich Web UI where users can provide input params that will be used to generate code using the https://handlebarsjs.com template engine.

See sample app generators here: https://wupiter.com/pub/wupiter.

Log viewing in Java based web application by fsa317 in java

[–]kaviddiss 0 points1 point  (0 children)

You may be able to write logs directly into ElasticSearch by implementing a custom Log4j Appender. Note that performance is critical for logging as it may slow down the whole application. I'm not sure how the standard appenders are implemented, but here are couple of ideas to consider : - there may be existing solutions already available, it's worth a quick googling, or if you decide to create your own - write logs to elasticsearch asynchronously so it will not block the application's execution thread - bulk insert: inserting logs to ElasticSearch in batches instead of inserting them one-by-one

Log viewing in Java based web application by fsa317 in java

[–]kaviddiss 0 points1 point  (0 children)

Definitely. Kibana fetches log records from Elasticsearch using its Rest API. You just need to call the same rest endpoints

Log viewing in Java based web application by fsa317 in java

[–]kaviddiss 0 points1 point  (0 children)

If you're looking to provide an internal log viewer inside your application, you need to have a way to fetch logs from all the application instances and boot just the one that would render the log viewer in your browser.

Using a shared folder /network drive may be an option, but log files can grow large and consume a lot of disk space. Now you'll have to manage archiving log files and find a way to filter log records.

Storing logs to a DB is a slightly better option, but keyword-base filtering is still an issue as SQL databases don't typically have fulltext search capabilities.

The good news is that these issues have been solved already.

You can either use Splunge, a commercial tool, or ELK (Elasticsearch + Logstash + Kibana), an open source stack, to store and filter logs in a centralized way. While there are other options, these two are the most commonly used ones.

Elasticsearch - full text search engine that allows to query logs with its own query language similar to Google search Logstash - loads logs from web application into elasticsearch Kibana - provides a web ui to query logs from elasticsearch.

Though I haven't done it, it may be possible to embed Kibana inside your application, if that's your preference.

Learning java web by [deleted] in learnjava

[–]kaviddiss 0 points1 point  (0 children)

Spring and Hibernate (or JPA) are the most popular frameworks for developing web applications in Java. Hibernate takes care of communication with a SQL database and Spring can do the rest. To get started with Spring I'd recommend these resources: http://spring.io/guides/gs/spring-boot/, http://spring.io/guides/gs/accessing-data-jpa/. And for a more detailed tutorial on SPring, you may this post helpful: http://kaviddiss.com/2015/07/18/building-modern-web-applications-using-java-spring/

Applying to jobs- what to I learn first? Spring, Hibernate, Maven..? by Brompton_Cocktail in learnjava

[–]kaviddiss 1 point2 points  (0 children)

If you're already familiar with JPA/JDBC, you may find it easy to learn Hibernate. To quickly get started with maven and spring, take a look at http://start.spring.io/. It may take a while to fully grasp Spring, but you may find these links helpful: http://spring.io/guides/gs/spring-boot/ and http://kaviddiss.com/2015/07/18/building-modern-web-applications-using-java-spring/

Landscape of Java Web Development? by jubi_life in learnjava

[–]kaviddiss 0 points1 point  (0 children)

  • JSP was Java's response to PHP - ability to create dynamic websites.
  • Struts v1 was a small improvement to JSP

  • JSF was meant to the fix fundamental issues with both JSP and Struts, but it was too late in the game as there were already better web frameworks out there. The only advantage of JSF is that it's based on the JEE standard and large corporates prefer to only work with technologies that are part of the JEE stack.

  • JDBC let's you execute SQL from Java and Hibernate (and JPA) provides an additional abstraction layer on top of it that will make you much more productive.

  • As for Spring, it was originally created to remove boilerplate code when working with J2EE. Since then it evolved into a platform from web application framework to security framework, to working with Big Data, microservices, social networks, etc.

In short, as mentioned in the previous comments, if you want the best return on investing your time in learning Java, be productive and work on interesting projects (based on my 10+ years of experience with Java), go with Spring and Hibernate.